Linked by lopisaur on Fri 25th Jun 2010 22:21 UTC
Permalink for comment 431618
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:
2009-10-04
I've never had a problem with it. X is designed to be able to do that, but I'm not sure how good the implementation is.
Well, maybe it can do that in some special cases, but I know that I've had Windows 7 and XP crash and bring down everything. My point is, in any OS, if a critical system component goes down, everything will go down. And Windows in general is more prone to this since it is more tightly integrated. Also, I've never had X crash, but I use only Intel hardware, which has very good drivers, so I understand that I'm not in the majority...
There is certainly nothing in X that prevents apps from not killing themselves if X crashes. The main problem is that right now, the toolkits leave a lot of state on the server. However, if you look at the design of Wayland, there is really no server state. The kernel stores the window surfaces. This means that it would be trivial for apps on Wayland to reconnect. The nice thing is that the same method is entirely possible with X too, toolkits are just lazy.
I don't think so. Enlightenment is gaining some usage with Samsung's Bada thing, but other than that, my guess is that its usage is declining.
This is just a myth popularized by Adobe (which is just using the myth as an excuse to be lazy). It's actually really simple. If you are writing anything to do with playing or editing videos/music, you use GStreamer. If you just want to play some simple sounds in your app, you use libcanberra. If you are writing a game, you use SDL. That's pretty much it. Those libraries will handle all the low level things that you don't need to know about. It's really not complicated...
True, it's not perfect. It still beats Windows, where every other app decides to draw its own ugly, unthemable widgets. Linux is certainly way more consistent in this regard. However, Mac OS X beats them both by miles.
Yes, it's really not realistic. I'm probably going to start using KDE soon, because I'm tired of GNOME not doing anything interesting in the last 5 years, and I really don't like GNOME-Shell.