News for hackers. Stuff that matters.
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by AceJohnny2 on Friday December 16, 2016 @03:00PM (#13196250)
One of the things I loved in Linux was the ability to swap out the "window manager", the program that takes app's windows, draws decorations like title bar and window borders around them, and arranges them on the screen. I had fun with Compiz, I fiddled with Enlightenment, and I finally settled for Awesome because I decided Tiling Was The Best (tm).

If I understand correctly from following the Gnome and KWin blogs, in Wayland it looks like the "window management" job is with the Compositor, which takes on a lot more of the display and input work that was traditionally handled by the X Server. So there's much more complexity to handle there. This would mean that we're unlikely to see the proliferation of WM experiments that X saw.

Is this a correct assessment?

(I'm personally waiting for a good tiling window manager/compositor to show up with Wayland before I make the swtich)

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by lomnakkus on Friday December 16, 2016 @03:13PM (#13196356)
> If I understand correctly from following the Gnome and KWin blogs, in Wayland it looks like the "window management" job is with the Compositor, which takes on a lot more of the display and input work that was traditionally handled by the X Server.

This is basically right. However, you have to remember that the Wayland protocol is at least an order of magnitude (if not two) smaller than X11. It's also defined/specced using a machine-readable XML document which means that an implementation of the protocol can basically be auto-generated from the spec document -- thus making it a lot easier to keep your implementation up to date.

> This would mean that we're unlikely to see the proliferation of WM experiments that X saw.

Remains to be seen, I guess.

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by digi_owl on Friday December 16, 2016 @03:18PM (#13196398)
Give W as much time as X11 has had, and it will be of comparable size as X11 is right now. They will perhaps try to play semantic games by putting much of the additions into support libs that you "don't need", unless you want to run anything more than a decade old.

Wayland, X11, SVGALib, F if i can tell a diff...

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by lomnakkus on Friday December 16, 2016 @03:24PM (#13196440)
No. It's already basically feature-complete as compared to which parts of X11 are actually used these days[1]. X11 is burdened by absurdly obsolete extensions like drawing stippled lines, a font server, etc. See the talk by Daniel Stone[2] if you're interested in the kind of crud that's been cleared out. It's basically the kind of stuff that we will never go back to wanting in any type of server process. The trade-off between bandwidth and latency has changed fundamentally in basically all areas of computing, but especially anything to do with graphics.

[1] Alright, there might be a few bits and bobs that are missing, but nothing major as witnessed by the very article under discussion.

[2] https://www.youtube.com/watch?v=RIctzAQOe44

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by digi_owl on Friday December 16, 2016 @03:35PM (#13196536)
Who gets to declare those things "crud"? I am sure that if you poke around you will find someone still relying on those features being present daily.
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by bitwize on Friday December 16, 2016 @04:22PM (#13196976)
Daniel Stone does. Maybe you get a say in it when you've spent as much time on the Linux graphics stack as Daniel Stone has.

Seriously, when's the last time you wrote a program that relied on the ability of the display server to draw stippled lines?

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by nitrogen on Friday December 16, 2016 @05:08PM (#13197338)
What's so bad about stippled lines? They sound useful for so-called "real work" applications for drawing grids and graphs and marching ants.
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by lomnakkus on Friday December 16, 2016 @05:54PM (#13197651)
It's not that stippled line are bad per se. It's just that they shouldn't be baked into a protocol that goes "over the wire" (so to speak). It's much faster if the program just gets a bitmap to draw on and draw the stippled line itself. It's important to note here that "itself" could mean that you just call a (Qt/Gtk/SDL/whatever) library function to do it.

There's no conceivable reason (these days) that you'd want to send a "draw a stippled line from point a to point b" command to an X server or graphics card.

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by nitrogen on Friday December 16, 2016 @06:20PM (#13197804)
I haven't done much 2D drawing recently. My intuition is that sending a batch of line/polygon/stipple/fill commands to a GPU would be more efficient than occupying a CPU and then using a bunch of memory bandwidth to transfer a bitmap. But on modern systems, software rendering to a bitmap in RAM is more efficient than sending a command to a GPU (which probably lacks dedicated 2D hardware)?
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by TD-Linux on Friday December 16, 2016 @06:57PM (#13198011)
GPU drawing can still be faster than on the CPU, and you can do that with Wayland, by directly opening the DRM device (/dev/dri/render*) and sending the rendering commands directly to the GPU. This is how Mesa implements OpenGL on both X and Wayland. The X way requires you to send XRender commands to the X server first, and then it sends them to the GPU. This was already too slow (hence the already existing bypass for OpenGL) and Wayland just extends that idea to all rendering.
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by digi_owl on Friday December 16, 2016 @07:29PM (#13198200)
Bingo. X was in part made for working over network and serial connections. And for that it works quite well when the clients play nice (async code between front and back end etc).

But the major toolkits have taken to rendering everything outside of X and just dumping the result as a bitmap into a box, that is absurd for all but the most local of work. And yet they complain about X being the problem.

X is not the problem. The problem is a generation of devs coming over from MS and Apple platforms and not recognizing that X is different. They just want to dump their eyecandy into the buffer and rely on Moore's Law for things drawing more than 1 pixel an hour.

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by espadrine on Friday December 16, 2016 @08:12PM (#13198442)
Blame is not on toolkits. The history is clear: came a point where MacOS X and Windows supported flawless animations with no screen tearing, and transparency, and antialiased rounded corners for windows.

Meanwhile, Linux still had blitted windows that left a grey trace for a brief instant when you moved them, and pixelwise window edges, and terrible transparency.

Came along Compiz, which reversed the way clients interacted with X, and which did the slick animations and fancy graphics of the mainstream OSes. What was the only way it found to do that? Rendering everything outside of X. And nobody could do it with the old design. So that design was quickly adopted by KWin and so on.

It turns out that nowadays screens are not lightweight clients over a serial line, and they have more than double the number of pixels of VGA.

Compositors became a necessity for the Linux Desktop to compete, reducing X to an IPC system that it cannot be good at, because it is not the situation it was built for. Wayland is built for the status quo.

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by bitwize on Friday December 16, 2016 @07:57PM (#13198328)
"Rendering everything outside of X" means directly accessing the GPU. Doing GPU stuff through X is slow and for DRI, the X server gets in the way. And X's 2D rendering primitives are obsolete. You want 2D primitives? It's called libcairo. Wayland provides the missing piece, the only bit of X anyone actually uses: providing buffers to clients to render into to be composited on the display.

Just about everyone who has worked seriously on Linux graphics agrees that X is a problem and Wayland is the solution. You might want to look into why they all say the same thing.

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by lomnakkus on Friday December 16, 2016 @06:42PM (#13197928)
RAM/DMA transfer is absurdly fast these days. (And "as a compositor" you'll have to do it anyway at 60fps, regardless.)
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by ibotty on Friday December 16, 2016 @05:17PM (#13197400)
> Seriously, when's the last time you wrote a program that relied on the ability of the display server to draw stippled lines?

or someone?

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by stinkytaco on Friday December 16, 2016 @05:39PM (#13197541)
Then they can implement stippled lines in their application. It seems absurd to expect X to support rarely used extensions simply because "someone" might use them. It's not like stippled lines are no longer allowed on the Linux desktop, you just can't hook into the desktop compositor to get them.
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by mgbmtl on Friday December 16, 2016 @04:06PM (#13196850)
You can usually tell by the very few people willing to maintain the code/feature. Some of it has layers upon layers of duct tape.
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by lomnakkus on Friday December 16, 2016 @06:03PM (#13197705)
The X.org developers decided. The person who started Wayland was an X.org developer, and IIUC many who joined the effort are/were X.org developers, etc.

> I am sure that if you poke around you will find someone still relying on those features being present daily.

Not really. Many of these things have been broken in X.org for years and years... because nobody used them! (Again, see the talk.)

There's also the whole abysmal security record of X11[1], due in large part to the huge API and the fact that all serialization/deserialization of requests is hand-coded (by necessity).

[1] https://www.youtube.com/watch?v=2l7ixRE3OCw

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by bonzini on Friday December 16, 2016 @03:45PM (#13196622)
xterm and rxvt do.
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by lima on Friday December 16, 2016 @03:24PM (#13196439)
> good tiling window manager

SirCmpwn is porting i3:

http://swaywm.org/

https://github.com/SirCmpwn/sway

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by cyphar on Friday December 16, 2016 @11:13PM (#13199158)
> > good tiling window manager

> SirCmpwn is porting i3:

It's not a port, it's a complete rewrite. You can't port i3 just because of all of the differences between X11 and Wayland.

Also, I would recommend anyone who uses SirCmpwn's several projects that they donate to him (he even made a free software project for dontations): https://drewdevault.com/donate/

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by nacc on Friday December 16, 2016 @03:07PM (#13196300)
There are a number of window managers for wayland already. The ArchWiki has a list of them [0].

[0]:https://wiki.archlinux.org/index.php/Wayland#Window_managers...

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by Tharkun on Friday December 16, 2016 @03:14PM (#13196374)
I'm heavy Awesome user myself. Pretty much refuse to use anything else these days. It works, doesn't get in the way and goes really well with my workflow.

It looks like the Awesome community currently has no plans for a Wayland port -- as it apparently wouldn't be trivial. Though someone mentioned that it might Just Work as a magical legacy X application. Can anyone confirm that?

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by digi_owl on Friday December 16, 2016 @03:15PM (#13196380)
And? Since E17, E has pretty much been a DE in its own right. Fueled in large part because Rasterman ran afoul Gnome and RH office politics during his stay at RH labs.

And E has a long history of supporting just about anything under the sun. You could even run its terminal "emulator" as an alternative tty on top of the Linux framebuffer if you so wanted.

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by AceJohnny2 on Friday December 16, 2016 @04:13PM (#13196896)
> Fueled in large part because Rasterman ran afoul Gnome and RH office politics during his stay at RH labs.

I recall Rasterman running afoul of pretty much every organisation he was part of... I recall issues with OpenMoko, an early linuxphone company, as well.

Re:Fedora 25: With Wayland, Linux has never been easier (or ... by stinkytaco on Friday December 16, 2016 @05:35PM (#13197524)
It also offloads several of the features of X to the clients. Including inter-process communication and networking. I suppose you can view this as good or bad, but it certainly much smaller and, in some ways, more efficient since I don't need to have the ability to network unless I load up an RDP.
Re:Fedora 25: With Wayland, Linux has never been easier (or ... by justinsaccount on Friday December 16, 2016 @03:04PM (#13196276)