|
Authored by: Wol on Wednesday, April 25 2012 @ 05:25 PM EDT |
Why shouldn't X survive? And why can't Wayland transition from MIT to LGPL?
After all, LGPL is a subset of MIT so it's not even as if it would take much
effort to change it!
Thing is, X is an ancient protocol, with lots of ancient baggage unsuited to the
modern world. I'm typing this on a remote-X desktop and it's dire if I'm doing
anything much more than plain text - that's over a 100Mb link!
I gather it's not particularly X that's to blame, it's just that things don't
work well together.
aiui, the aim initially is for X to sit on top of Wayland to isolate it from the
hardware (which will fix many of the problems with X, like needing root rights,
like my problem of dire graphics, etc etc). But then, if Wayland gets network
transparency (which I gather is not planned particularly, but is perfectly
feasible) then X will be obsolete and will just fade away as "a tired old
protocol that has been superceded".
Cheers,
Wol[ Reply to This | Parent | # ]
|
|
|
|
|