| |||||||||||||
Wayland and Weston 1.0 releasedWayland and Weston 1.0 releasedPosted Oct 24, 2012 17:41 UTC (Wed) by daniels (subscriber, #16193)In reply to: Wayland and Weston 1.0 released by gurulabs Parent article: Wayland and Weston 1.0 released
Yeah, it does read quite badly. If you keep on reading, you see it arrive at the real answer of 'yes, it's coming, we just don't think it belongs in core protocol', but unfortunately it starts from a pretty literal interpretation of the question.
Sorry about that. :)
(Log in to post comments)
Wayland and Weston 1.0 released Posted Oct 24, 2012 18:02 UTC (Wed) by apoelstra (subscriber, #75205) [Link]
> Yeah, it does read quite badly. If you keep on reading, you see it arrive at the real answer of 'yes, it's coming, we just don't think it belongs in core protocol', but unfortunately it starts from a pretty literal interpretation of the question.
> Sorry about that. :)
Thanks for your polite replies in this thread. Myself, and I suspect many others, don't take the time to read up on this stuff, and only encounter Wayland discussions on LWN. And as you say, there are many armchair software developers slinging crap around, and the communication from the Wayland devs thus far leaves something to be desired.
So, it's nice to see people rising above the fray and clearing up misconceptions, rather than getting caught up in flamewars (or completely ignoring the thread).
Wayland and Weston 1.0 released Posted Oct 24, 2012 22:31 UTC (Wed) by rahvin (subscriber, #16953) [Link]
As one of the armchair idiots let me just say I was right along with everyone else's negativity until I read the excellent LWN articles and subsequent wayland developer comments that were in replay to the article. Wayland appears to me that it's going to solve some real problems, remove some serious legacy cruft (almost 90% of X isn't even used) and bring the Linux desktop back to the Unix approach which is a simple tool for each task and X is not a simple tool.
The worst part is the misunderstanding about what Wayland is and what it's trying to do as can be seen in the slashdot article and unfortunately in the posts here as well. (as noted, it doesn't help that the FAQ is badly worded in some cases).
Wayland and Weston 1.0 released Posted Oct 25, 2012 0:14 UTC (Thu) by nix (subscriber, #2304) [Link]
Agreed. I'll only be unhappy with Wayland if major toolkits don't bother to implement remoting -- but if they do (which seems likely, or Wayland will never take off), it's probably going to become as capable as X already is, with more scope for expansion.
Wayland and Weston 1.0 released Posted Oct 25, 2012 15:08 UTC (Thu) by renox (subscriber, #23785) [Link]
> Agreed. I'll only be unhappy with Wayland if major toolkits don't bother to implement remoting
I think that "a proxy pushing giant bitmap" remoting will be eventually available whatever the toolkit used, of course in some case (text) it's quite inefficient compared to XRender glyph cache's remoting..
Wayland and Weston 1.0 released Posted Oct 25, 2012 22:52 UTC (Thu) by rahvin (subscriber, #16953) [Link]
The only thing I can do is point to the comments in the previous articles that even if you are running Wayland you can still run X on top even if someone doesn't do a connector or other tool that only runs the parts of X that are needed.
Wayland and Weston 1.0 released Posted Oct 27, 2012 8:22 UTC (Sat) by paulj (subscriber, #341) [Link]
The major toolkits already implement remoting that works with Wayland: X11. Hopefully there'll be better remoting protocols in time.
Wayland and Weston 1.0 released Posted Oct 28, 2012 16:01 UTC (Sun) by nix (subscriber, #2304) [Link]
True! So we *already* have nothing worse than before, as long as someone keeps the X11->Wayland stuff maintained (and I suspect, given the installed base of X applications, that it's not going to fall unmaintained for a long, long time).
|
|||||||||||||