Wayland 1.7.0 Marks an Important Release
jones_supa writes: The 1.7.0 release of Wayland is now available for download. The project thanks all who have contributed, and especially the desktop environments and client applications that now converse using Wayland. In an official announcement from Bryce Harrington of Samsung, he says the Wayland protocol may be considered 'done' but that doesn't mean there's not work to be done. A bigger importance is now given to testing, documentation, and bugfixing. As Wayland is maturing, we are also getting closer to the point where the big Linux distros will eventually start integrating it to their operating system.
Remoting should be done at the toolkit level. This is where it belong. Similarly to sftp, gtkclient->ssh->intertubes->ssh->gtkapp
in practice you would call "gtkclient user@host:/path/to/gtk/application" which would connect the ssh pipes, set envar GTK_BACKEND to "pipe" and run the app. Gtk api get serialized both way, piped through ssh and run locally on your gtkclient which use what ever display backend your desktop is set to. This way you get the absolute minimal network traffics with zero lag in display. eg; highlight and scroll are just like local application.
I am unqualified to make this a reality so no amount of 'it open source, do it yourself' is going to help. I am just complaining here because I can. Thanks for your time.
From my poorly-informed vantage point, it seems like all the things that truly sucked about X Window are still there in Wayland.
Is there any good reason to use Wayland rather than X Window?
<rant>
For those of us who have not heard of Wayland, the following is how the summary reads:
The x.y.z release of Some Software is now available for download. The project thanks all who have contributed, and especially the desktop environments and client applications that now converse using Some Software. In an official announcement from Some Author of Some Company, he says the Some Software protocol may be considered 'done' but that doesn't mean there's not work to be done. A bigger importance is now given to testing, documentation, and bugfixing. As Some Software is maturing, we are also getting closer to the point where the big Linux distros will eventually start integrating it to their operating system.
So what does Some Software actually do and why should I be interested? I know that I can Google Some Software, but is it really that hard to start with the summary with the following:
The x.y.z release of Somesoftware, a package which does blah blah blah, is now available for download. ...
After all, phrases such as "As Wayland is maturing", imply that this is a relatively new piece of software still under development of which everyone is not familiar, especially for those of us using BSDs, Solaris, and Slackware.
</rant>
> She died of cancer in 1977.
Which means you're old enough to know better than to engage with angry, irrational children. Next time just ignore them rather than arguing with them. They obviously think that those of us that care about a script's exit status, stedrr not being logged in the journal, or high priority syslog messages being dropped are just old and out of touch. You're obviously not going to convince them with facts and logic after they're so emotionally (well, anger anyway) invested in defending their pet project.
The debate is not exactly symmetric: One side has built a certain software that has been adopted by all mayor linux distributions. The other side has built nothing but flamewars.
this post contain no useful information, no need to mod it down