Wayland 1.2.0 Released With Weston 122
An anonymous reader writes "Wayland 1.2 & Weston 1.2 have been released. Features of this quarterly update to the X.Org/Mir display competitor is support for color management, a new input method framework, a Raspberry Pi renderer/back-end, HiDPI output scaling, multi-seat improvements, and various other changes for this next-generation Linux desktop display protocol and compositor."
Looks good! (Score:5, Interesting)
Wayland & Weston are coming along pretty well and we are seeing increased adoption in both GTK+/QT toolkits and in desktops with upcoming versions of KDE.
One area where the developers need to go out and evangelize is on the front of EGL for proprietary drivers. Yes it's great that Intel's open source drivers (and to a lesser extend the open-source AMD & Nvidia drivers) have EGL support, but both AMD & Nvidia need to be convinced that EGL is important to their upcoming proprietary drivers too.
The irony here is that Mir, which is is seen as a huge competitor to Wayland, could end up helping Wayland enourmously since Canonical doesn't seem to be afraid to pick up a phone and call people at AMD/Nvidia to talk about updating the drivers.
Re:Wrong Summary (Score:1, Interesting)
Except it's complete bullshit. Read the announcement: Wayland 1.2.0 now provides a stable server API (it already provided a stable client API since 1.0.0) as well as a rigid protocol. Everything, everything, that has been said about Mir being better then Wayland is Grade-A Pure Bullshit. Also, Mir will lose because nobody else is ever going to use it. Wayland: all Linux distros except Ubuntu (including all commerically supported distros like SLE and RHEL). Mir: only Ubuntu. Hell, even the Ubuntu derivatives like Kubuntu and Xubuntu have publically stated they won't use Mir!
Re:Benchmarks please (Score:2, Interesting)
Re:Benchmarks please (Score:1, Interesting)
Actually, your observation is misleading. Graphics drivers on Linux have been using a lot of Linux features for a long time to improve performance, implement modern features, and handle hardware management in the kernel, where it belongs. No rule says that code can then only be used by X. They are Linux drivers, not X drivers.
Re:Benchmarks please (Score:4, Interesting)
Sure.
Speed of light 186,282 miles per second .0683 seconds
Speed that a human can detect jitter of an icon tracing a finger 1/100th of a second
size of the earth 26k miles
circumference of the earth 24,901
fastest possible a round trip can occur from the worst 2 spots on the earth assuming 0 latency beyond the speed of light:
or the earth is about 7x too big for X11 to work.
Chance of us being able to fix either the speed of light or the size of the earth 0%
Remoteability question restated (Score:5, Interesting)
Here's a very simple question with hopefully no wiggle room: Suppose I have two Linux boxes, each running Wayland. They do not run X11 in any form or fashion. I am on the console of one of them and in Wayland. Can I start a terminal emulator, ssh over to the other box, issue a command that starts some graphical program (which uses only Wayland coding, no X11), and expect that program's window to show up on the first box? Assume that ssh has already been modified to allow for this sort of thing. If this cannot be done, what prevents it from being done? I have yet received no complete answer for this.