There was an article on this on Slashdot recently - cruft. The gist of the story is that programmers make these great systems intending to clean up the code later, but they never do. The article lashed out in equal doses against both OSS and proprietary s/w.
Sorry I don't have the link. The problem with X is that all your gui programs expect to find an X server to connect to (specified by the $DISPLAY environment variable IIRC). Replace X and you'll have to provide something that _looks_ like X to any app looking for a display to connect to. IFAIK widget sets like QT and GTK provide a layer of abstraction so apps based on these libraries don't have to talk "X protocol". Therefore, a version of these libraries that talks to the graphics hardware directly might eliminate the need for X. I believe such versions are available for these libs. Yuri >i've always thought that the downside to open source OS' is >that things are extended and modified but the guts of the programming usually remains the same... > >i mean the concept of X has not really had any other competition >has it? >we all no it has limitation in speed etc, but the choices we have >are only modifications of it. you'd think that if there was money to >be made, that this would happen and groups would take the plunge creating ingenius new systems... >but then you see microsoft, and the same old stuff coming out of it >for years. >maybe it's just how things work, but when you look at the freedom >that programmers have, it's almost pure design. >in a free environment you expect them to reach for the sky-
