Linked by David Adams on Mon 24th Aug 2009 09:21 UTC
Permalink for comment 380569
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 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
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2009-06-11
Ok, besides the fact that everyone is used to X and every distro, every flavor of *nix has an implementation, what is the problem with starting out with a clean slate? X has code that dates back to a time when c compilers probably didn't support passing structs as arguments by value, among other things, which contributes to the brain dead way Xlib handles windows and displays.
Seriously, would you like to tell me that the documentation for X is good, that X provides a clean interface to the coder for working with windows and displays? I think you are just comfortable with it.
Again, why would a clean slate be a bad thing? A linux-based os meant primarily as a desktop does not need X's feature set. Wouldn't it be nicer to have something smaller, better documented, more sanely designed, and again, something that has less impact on the end user's system resources?
I'm sure you're quite intelligent, and know what you're talking about when it comes to a discussion of the relative merits of X.org (my apologies for my terse reply yesterday, I had just woken up and was cranky- no excuse for being a jerk though). I'm not saying X has to die. X isn't going to die anytime soon. I just want to know why a new windowing system designed without 20+ years of legacy hanging from it's neck is a bad thing? --Provided it supplied the features that were needed to supply a modern end user experience, and achieved the goals of being developer, end user, and system friendly, which I argue that X really isn't.
So maybe I'm guilty of blankly stating a preference for a clean slate design over X without listing all the reasons that this would be a good idea. I'll admit that you are probably in a better position than I am to intelligently discuss the relative merits and shortfalls of X.org. I still ask, what is the problem with a new system that achieves the goals I expressed? OS X certainly provides a nicer end user experience than FreeBSD running X. Why would a linux-based solution (Chrome OS) with a new, proprietary windowing system be such a bad thing?
Edited 2009-08-25 19:53 UTC