 Re: Obsoleteness of X concept
On Aug 13, 6:23*pm, Temoto wrote:
> [cut]
Now thanks to responders i see three major parts that X is compound
of.
1) video driver, renderer
For video drivers there are solutions like, well, drivers in Windows.
2) remote desktop (even if it goes to local desktop in optimized way,
such as shared memory)
For remote desktop there are solutions like VNC.
3) generalized UI, hardware abstraction (program that wants to
interact with user, interacts with X instead of kernel and drivers)
Hardware abstraction is nonsense for me, since there are configurable
makefiles, plugins, versioning and so much abstraction possibilities
to build, say, window manager running just fine directly with video
drivers. And this layer is not complete, because there is no sound and
printers support in it. Maybe something important too.
Actually i hate this point most of all. Because i see least of
usefulness here.
And i feel this is not UNIX "one small program making small job
perfectly" way. In my imagination's perfect world, X should be
splitted into three separate programs, handling those three separate
tasks. Oh well better in 2 separate programs since third is not
needed. Oh well just become a video driver.
Isn't that right?
 |