Linked by lopisaur on Fri 25th Jun 2010 22:21 UTC
Permalink for comment 431623
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-02-15
Try to play with it when some heavy calculation is running in the background, and see if it remains responsive ^^
Are you saying that X becomes unresponsive if you have heavy calculation in the background? If so then you're just talking out of your rear-end. I often compile stuff and as you should know compiling IS rather CPU intensive. And I haven't noticed any kind of lag or issues with responses from X.
Wrong. If windows' graphic layer crashes, and I've seen it crash many times, the desktop disappears for a moment, then reappears with all your apps on top of it. You can safely save your work before rebooting your computer and investigating what's wrong if crashes happen again.
True, indeed. And surprisingly many people insist that X and Windows act the same in this regards but they don't: I've had X crash several times and it took down everything I had open, including a coding session I hadn't saved for half an hour. But I've also had Windows graphics layer crash, in XP and in 7, and all that happened was that the screen went black for a moment and then got back, with all my apps still intact.
What does this mean? Well... that even the god damn old XP handles this thing better than X!