| |||||||||||||
Bad NIH, good NIHBad NIH, good NIHPosted Mar 10, 2013 3:07 UTC (Sun) by HelloWorld (guest, #56129)In reply to: Bad NIH, good NIH by Serge Parent article: Canonical reveals plans to launch Mir display server (The H)
People have explained dozens of times by now what's wrong with X11 and why it's worth working on a replacement. If you still didn't understand, it's because you don't want to, and I won't waste my time trying to convince you otherwise. Fortunately, the world keeps moving despite stick-in-the-muds like you.
(Log in to post comments)
Bad NIH, good NIH Posted Mar 10, 2013 15:37 UTC (Sun) by hummassa (subscriber, #307) [Link]
> People have explained dozens of times by now what's wrong with X11 and why it's worth working on a replacement.
No. No one has explained what is wrong with X11 or with its implementations.
More specifically, no one has explained why any possible flaws are not fixable.
About the worth of working on a replacement, to each its own, and no one can force others to work (or to pay someone to work) on something.
Bad NIH, good NIH Posted Mar 10, 2013 18:25 UTC (Sun) by patrick_g (subscriber, #44470) [Link]
> No. No one has explained what is wrong with X11 or with its implementations.
Please look at this video : http://www.youtube.com/watch?v=RIctzAQOe44
Bad NIH, good NIH Posted Mar 11, 2013 4:58 UTC (Mon) by Serge (guest, #84957) [Link]
>> No. No one has explained what is wrong with X11 or with its implementations.
> Please look at this video : http://www.youtube.com/watch?v=RIctzAQOe44
Presentation that starts with "Noone has any idea". Saying things like "I'm the smart guy and everybody else is stupid", even if you're joking or have reasons for that, still looks... not very polite. But let's get back to the X11 talks.
There goes an interesting story of XFree86/Xorg evolution, how it looked 20 years ago and how few features it had back then, and how many features it has now, how it adopted all the modern hardware, how older extensions were replaced by their newer versions etc.
But where are the problems? Gedit startup is too slow? Then fix gedit! The rest is like "X is doing that bad, so Wayland can't do that at all" or "X does it that way, we don't like that, so Wayland does it this way" or usually it's like "Wayland is going to do it better" because it's not implemented yet or the implementation is very basic/buggy. That's all! No problems of X11 protocol or even Xorg there.
What have I missed?
BTW, it was kind of fun listening to "X isn't network-transparent any more" while running some GUI tools over ssh -Y.
Bad NIH, good NIH Posted Mar 11, 2013 9:30 UTC (Mon) by gioele (subscriber, #61675) [Link]
> BTW, it was kind of fun listening to "X isn't network-transparent any more" while running some GUI tools over ssh -Y.
The presenter explicitly said that "X is network-capable, not network-transparent". It means that you can run X applications over the network, but the software has to handle it as a special case now, given that the current normality is the use of shared memory buffers.
Bad NIH, good NIH Posted Mar 11, 2013 4:33 UTC (Mon) by Serge (guest, #84957) [Link]
> People have explained dozens of times by now what's wrong with X11 and why it's worth working on a replacement.
No! People have dozens of times explained why they CAN work on a replacement, not why it's worth working on it. Usually all those explanations boil down to "X11 has too many features" and "Wayland is not too bad". But nobody have ever explained who's going to win from it. I would be glad if you provide me a link to such explanation.
Wayland/Weston is like a HelloWorld-program. It's useless but IN THEORY you can extend it to do whatever you want... Hm... HelloWorld is the best graphical manager! It's fast and simple! You can do everything else client-side! Sounds familiar? :-)
|
|||||||||||||