News for hackers. Stuff that matters.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by d3nj4l on Thursday June 30, 2022 @09:55PM (#31941260)
I think it's fascinating how general opinion seems to be becoming more neutral on Wayland compared to the rah-rah days I remember, probably around 2018-19. I personally could never use Wayland - I was pretty set in my i3 config, so GNOME switching to Wayland didn't affect me, but I always had PCs with nvidia GPUS (I like playing games, sue me) and while admittedly, nvidia wasn't working on good faith either, I don't think nvidia users deserved the attitude they got from eg. Sway. Despite that, the amount of effusive praise Wayland got on HN and some linux-centric communities had me jealous. What changed over time? I see that this gist was made in 2020, was it the issues with screensharing that became more pronounced due to COVID induced WFH? Did some major distro enable Wayland by default and therefore brought people out of the woodwork? If someone knows what the history is here I'd be delighted to know.

Of course, it's entirely possible I'm misreading the history here: Wayland could've been widely despised back then, or maybe this thread is an outlier. Either way, I'd be happy to see if anybody's got a good pulse check.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by indolering on Friday July 01, 2022 @12:09AM (#31942246)
I have had the opposite experience: fewer people making bad arguments against Wayland and more competent commentary overall. I also can't remember a time when X Windows was seen as being well engineered and not being in need of replacement.

Virtually all of the complaints listed in this rant are the result of enforcing a sane security model.

> I absolutely detest it when software tries to prevent me from doing what some developer thinks is "a bad idea" but did not consider my use case, e.g., running truss for debugging on FreeBSD needs to run the application as root.

These are not compelling arguments for running the GUI as root or allowing different applications to spy on each other.

I suspect the rationale behind this rant is motivated by the author's position as a BSD distro manager. BSD people really dislike it when Linux replaces legacy Unix infrastructure with Linux specific technologies. But if Wayland is doomed as an Xorg replacement, then why has development activity dropped off [0][1]?

[0]: https://www.phoronix.com/scan.php?page=news_item&px=X.Org-Se... [1]: https://www.openhub.net/p/x

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by ranguna on Friday July 01, 2022 @03:08AM (#31943338)
The safest computer is a turned off computer buried in concrete, would you use that as your daily driver?
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by indolering on Saturday July 02, 2022 @03:45AM (#31957051)
I'm sure I would have driven a 1960's death trap [0] given that was the only option at the time.

[0]: https://en.wikipedia.org/wiki/Unsafe_at_Any_Speed

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by ranguna on Sunday July 03, 2022 @06:20AM (#31966575)
Good thing you have x11 and wayland then, for those that want all the features out of the box and don't want to handle the hassles of restricted gpus or installing a package for each feature: just go x11. Else, yeah, wayland I guess.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by pmarreck on Saturday July 02, 2022 @02:45PM (#31961338)
I have no vested interests (other than being a RescueTime user who likes apps that can also create global keystrokes) and I also think it's a bad model. I as a user should be able to trust a piece of GUI software to have privileged access to certain things; that usually means running as root. If there were a way to define a role which was privileged but only in certain areas (such as RescueTime getting access to all window titles and perhaps some contents but that's it), then that would be a possible argument against running as root, but no such thing has been proposed here.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by indolering on Sunday July 03, 2022 @08:01PM (#31972080)
I agree! I can't imagine such a thing hasn't been proposed, as it is required by accessibility software.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by legalcorrection on Friday July 01, 2022 @01:21AM (#31942668)
It's not a sane security model if the product doesn't do what the users need it to do as a result.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by vetinari on Friday July 01, 2022 @03:54AM (#31943617)
It does. Just not with gates wide open.

For example, screenshots. It is still possible to make screenshots. It is not possible to make screenshots without the user knowing. What use case do you have to make screenshots without user knowledge, that benefits the user?

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by michaelmrose on Friday July 01, 2022 @08:08PM (#31954656)
Corporate computers frequently make screen shots or screen recordings of employee interactions.

The benefit of being wide open is that no coordination is needed between desktop environment and developer leading to a wide open field of tools that work on every environment without exception, difference in feature set, no need to check if version foo works on version bar of $DESKTOP.

You could of course get virtually the same benefits plus improved security at the cost of some complexity by standardizing the feature in common usage for nearly 30 years towards the beginning of the development cycle of Wayland instead of 13 years in.

You point out the need for security and completely ignore the fact that such security could trivially have been obtained without reducing users to obtaining a pile of tools only from their desktop environment or waiting 20 years for things to standardize so they can again pick and choose the best tools for the particular task.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by indolering on Saturday July 02, 2022 @03:57AM (#31957096)
> Corporate computers frequently make screen shots or screen recordings of employee interactions.

It's not like they haven't figured out how to do that with Windows or OS X.

> The benefit of being wide open is that no coordination is needed between desktop environment and developer

The same is true of virtual memory.

> You point out the need for security and completely ignore the fact that such security could trivially have been obtained

The Xorg developers who tried really hard for decades would disagree with you. That's why programmers that Red Hat used to pay to hack on Xorg now get paid to develop Wayland [0].

[0]: https://www.theregister.com/2020/10/30/x_server_lead_maintai...

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by michaelmrose on Saturday July 02, 2022 @09:53AM (#31958989)
> The Xorg developers who tried really hard for...

You misunderstand. Wayland development started in 2008. Screenshots/recording should have been on the board from day one and they could have gotten to standardizing on how to handle them in oh 2013-2015?

The sin is not the extra complexity to secure the system. It's having first zero then more than one way to go about it and 13 years later ending up in the situation where some utilities support only X and some only some Wayland implementations. It's the sin of forcing your users to rip out the walls and stare at the plumbing.

What other OS makes you think about display servers?

Red Hat doesn't believe in the Linux ecosystem and it shows they believe in their ecosystem with a singular official GUI and unfortunately an ecosystem in which one is required to use only their tools is a mostly mediocre one because they are best in class in nothing and worst in class in many.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by indolering on Sunday July 03, 2022 @07:55PM (#31972042)
> Screenshots/recording should have been on the board from day one and they could have gotten to standardizing on how to handle them in oh 2013-2015?

I agree that Wayland's development has taken far too long and the transition has been rocky. But what development team couldn't use more funding? Ubuntu throwing a tantrum after the ecosystem rejected Mir and not contributing to Wayland certainly didn't help.

> What other OS makes you think about display servers?

I am sympathetic to arguments that Wayland/Weston could provide more functionality out-of-the-box. The bazaar's fragmented mess of "desktop environments" is certainly not a strength compared to what the Cathedrals have produced. But Linux's uniquely modular GUI stack necessitates coordination across lots of projects to develop and adopt standards.

But not doing anything and sticking with X11 would have condemned us to being stuck with an insecure, buggy, and visually glitchy mess forever.

> Red Hat doesn't believe in the Linux ecosystem

I have my qualms with Red Hat too, but my point was that Wayland was created by Xorg developers because they tried and failed to make X11 competitive. Seriously, just go watch this XFree86/Xorg/Wayland developer's talk [1].

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

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by michaelmrose on Monday July 04, 2022 @06:36PM (#31982436)
> The bazaar's fragmented mess of "desktop environments" is certainly not a strength compared to what the Cathedrals have produced.

I will have to disagree. I like having options. Before Wayland having options meant that your app starting GUI and your file manager was different. If Wayland had meant there were now two options one deprecated and the other coming this wouldn't have really been a huge problem.

It's a problem now because insisting on standardizing on so little means we now have fragmentation the likes of which we never had with X and will likely have for many years to come.

Even more so because it isn't yet ready about 6 years after its fanboys started insisting it was and shitting on other options and dismissing actual problems as the mutterings of crackpots and luddites.

What does "competative" even mean in this context? Linux has had a nicer GUI since 2003 and if you don't hop on the pointless change parade a fairly consistent one. I literally switched to linux for a better interface 19 years ago and its still better.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by indolering on Wednesday July 13, 2022 @08:48PM (#32090623)
> I will have to disagree. I like having options. Before Wayland having options meant that your app starting GUI and your file manager was different. If Wayland had meant there were now two options one deprecated and the other coming this wouldn't have really been a huge problem.

I agree that the transition has been long and messy. But the Linux desktop experience has always been a fragmented mess of half-baked apps that quickly fall into disrepair. Wayland breaks a lot of stuff that has been in maintenance mode for a long time. That sucks, but it's not a good argument for sticking with X11. The situation with X11 had been unacceptable ever since the adoption of virtual memory and Wayland is the only real alternative.

> It's a problem now because insisting on standardizing on so little means we now have fragmentation the likes of which we never had with X and will likely have for many years to come.

I'm not going to criticize the boundaries of a standard that I haven't been deeply involved with. I understand their impulse to keep it minimal, as Wayland is something of a forever standard. But I am sympathetic to arguments that Wayland doesn't do enough.

> Even more so because it isn't yet ready about 6 years after its fanboys started insisting it was and shitting on other options and dismissing actual problems as the mutterings of crackpots and luddites.

If by "other options" you mean Mir, my memory is that the primary criticism of Mir's original architecture replicated Wayland in an incompatible way without any good reason for doing so. Eventually Mir was re-architected to layer it on top of Wayland and does provide more of the batteries you seem to want to have by default.

If by "other options" you mean X11 ... only crackpots and luddites think applications should be able to spy on each other [0].

What other options were there?

> What does "competitive" even mean in this context?

* Not having every app double as a key-logger.

* A working screen-locker.

* Not tearing on window resize or scrolling while a video plays.

* Multi-DPI monitors.

* Non-blocking API calls.

* etc [1].

I remember context menus being especially glitchy.

> Linux has had a nicer GUI since 2003 and if you don't hop on the pointless change parade a fairly consistent one. I literally switched to linux for a better interface 19 years ago and its still better.

Let me guess, you use some "minimalist" desktop environment? I'm not here to hate on people that don't need what most consider a modern user experience. If that's what you want, that's great! I was into lightweight desktop environments for a while and liked exploring that design space.

But I'm also a usability engineer who remembers Linux back then: it was not competitive with OS X and it still isn't.

[0]: https://en.wikipedia.org/wiki/TempleOS

[1]: https://www.phoronix.com/scan.php?page=article&item=x_waylan...

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by michaelmrose on Friday July 15, 2022 @08:39PM (#32114264)
=================================================

* HALF BAKED

=================================================

> But the Linux desktop experience has always been a fragmented mess of half-baked apps that quickly fall into disrepair.

> Let me guess, you use some "minimalist" desktop environment?

You mean the environments which aren't half backed and instead of falling into disrepair just sit there quietly working the same way so you can use your computer to do useful things?

=================================================

* WAYLAND SECURITY

=================================================

Millions of people have apparently solved the keep applications from secretly hacking you for man eons and decades of real time by not installing uncle bobs malware from www.notarealsite.com or responding to prompts to install software by fake support scam agents.

This is admittedly inferior to better isolation but better isolation is quite hard and few people are actually tackling it in any meaningfully complete way. If I solely switched today from X to Wayland I wouldn't meaningfully improve my security because apps aren't strongly firewalled from one another and so many vectors exist its more like installing a screen door than a bank vault. Proposed improvements like flatpak actually greatly reduce security in practice by

- Allowing users to be targeted by targeting already fixed vulnerabilities in flatpaks with outdated libraries

- Making it MUCH easier to get random bobs software in front of the user

- Trivializing the gap between compromised developer and user by shortening the gap between compromise and distribution from days->weeks to minutes->hours.

All told security is on net a pretty pointless reason to switch to wayland at this point. See qubes, distro processes, FDE, user education about common scams for actual improvement in security.

Lets be real you knew I didn't mean MIR.

=================================================

* COMPETITIVE POINTS

=================================================

- Tearing: I didn't have this problem in 2003 and I don't have it now.

- Multi-DPI monitors: I am typing this on a machine with a 4K monitor flanked by 2 1080p monitors. I scale them down from a higher resolution. Apps think all 3 are the same DPI and its transparently scaled down so that UI elements are identically sized on all displays. Nothing is blurry.

- Non-blocking API calls. I'm using an environment not writing one. None of your users on earth care.

=================================================

* SECURING LOCKED COMPUTERS

=================================================

On desktop machines screen locking provides by default similar levels of security as locking a bathroom door it protects against casual intrusion. You can keep someone from sitting down and looking at your email it cannot prevent an attacker with physical access to your computer from gaining access to your data.

You could get greater security by blocking switching TTY and by blocking usb devices from being attached while the screen is locked for example with USBGuard regardless of choice of display server.

https://usbguard.github.io/

For machines that are at risk of actual attack you would want to to rely on FDE and either full shutdown or locking critical data when user isn't in physical control of the device.

None of this has much to do with choice of display servers and choosing Wayland by default doesn't appear to do much beyond what could be accomplished by blocking changing ttys.

=================================================

* END LINKS

=================================================

I'm not sure why you linked either TempleOS or a 9 year old write up on the design flaws of X.

For what its worth its not only dated but bad as well. Just to pick on a particularly bad patch.

>Wayland breaks everyone's desktop.” Also wrong. Once XWayland is finalized and merged we should have more-or-less perfect backwards compatibility because every X app just gets its own mini X-server to deal with.

This was back in 2013 and the entire ecosystem has spent 9 years going through growing pains with applications going through a plethora of Wayland specific issues with entire categories of applications disappearing or requiring different implementations on different compositors years later. In 2013 this was basically the definition of over-promise under-deliver. It's aged like milk and it makes the authors analysis challenging to take seriously.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by hulitu on Friday July 01, 2022 @04:26AM (#31943793)
On my computer i know (except for the web browser) which program makes screenshots. I want all my programs to function properly but not send my data over the internet. So i really don't see the problem Wayland is trying to solve (web browser still executes remote untrusted code).
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by vetinari on Friday July 01, 2022 @05:12AM (#31944052)
Does your OS use protected memory?

Why? If you knew all your programs, and that they are well-behaved, there is no need for that.

But we do use protected memory. And IOMMU (you know all the peripherals that you connect to your computer as well, right?). And other facilities intended to separate programs and hardware from each other.

So the same way as programs do not snoop on shared global heap, do not big-bang i/o ports, etc, programs are not supposed to snoop on shared display surfaces (really just a subset of 'global shared heap'). If you need something specific from them, you ask them via defined way (e.g. screenshot API), that might or might not have facilities to enforce access control.

Because we are not relying on them to be well behaved. Instead, we will notice if they aren't.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by michaelmrose on Friday July 01, 2022 @08:10PM (#31954672)
If protected memory was implemented somehow per desktop environment and relegated me to choosing between Gnome and KDEs respective browsers/office suites instead of installing Firefox and Emacs I would either eschew it and take the risk or give up on Linux entirely and get a Mac.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by indolering on Saturday July 02, 2022 @03:42AM (#31957034)
> If protected memory was implemented somehow per desktop environment

I'm sure LOTS of people stopped using certain Unix programs that relied on a single address space whenever that was implemented. But to quote myself a few relies up,

>> These are not compelling arguments for running the GUI as root or allowing different applications to spy on each other.

> or give up on Linux entirely and get a Mac.

You mean the Unix that originally decided against using X11 because it would have required a re-write to do what they wanted anyway [1]? You understand that Wayland was designed by core Xorg contributors to replace X11 because attempts to match OS X resulted in a glitchy nightmare ... right?

[1]: https://news.slashdot.org/comments.pl?sid=75257&cid=6734612

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by btschaegg on Friday July 01, 2022 @04:23PM (#31952299)
"I was merely endeavoring to indicate that if we do not grab events by the collar they will have us by the throat."

SCNR :)

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by vetinari on Sunday July 03, 2022 @07:20AM (#31966849)
Yup, exactly :-D
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by pmarreck on Saturday July 02, 2022 @02:48PM (#31961352)
> What use case do you have to make screenshots without user knowledge, that benefits the user?

Headless browser testing. Network admin at a corporate site. For starters.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by vetinari on Sunday July 03, 2022 @07:23AM (#31966862)
You can do headless browser testing with virtual screen, that doesn't need real one.

For corporate uses, you can use something like vPro and it's remote access. It works independently of the OS (and by default expects user consent too).

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by indolering on Sunday July 03, 2022 @06:46PM (#31971648)
There is a sane API for this use case on every major platform. The argument is that X11 made a mistake by allowing it by default.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by kelnos on Thursday June 30, 2022 @10:11PM (#31941384)
Yeah, I still have yet to try Wayland (Xfce user here, which I expect may never port), and I never really got the hype. I honestly just don't get all the gripe people have about X11. I think all the current problems (including the security issues) are solvable through new extensions, if someone wanted to take the time to work them out. Given that But no, it's better to throw everything out, start from scratch, create a ton of new work for people, and 12 years later still not have displaced X11.

Put another way: do we truly believe that in 12+ years, some motivated hackers couldn't evolve X11 into something better? I get that many of the people involved were burnt out on it, and sure, no one (myself included) stepped up to the plate, but it doesn't seem plausible to me that X11 and Xorg are lost causes.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by kaba0 on Friday July 01, 2022 @04:20AM (#31943755)
> Put another way: do we truly believe that in 12+ years, some motivated hackers couldn't evolve X11 into something better?

Yes. It is not just a random program that needs some fixing here and there, it is a program which has to evolve with all its accompanying user space, as almost anything can be a breaking change. Sometimes reinvention is the correct decision, and I am quite sure that the whole X11 team uniformly deciding on that gives it enough weight.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by MBCook on Thursday June 30, 2022 @10:39PM (#31941590)
In 12 years they probably could have improved X a lot. But the impression I always got (years ago when this was a bigger topic) is it likely would have broken backwards comparability to do right. And if it’s not compatible, is it still X? And would the Wayland haters/holdouts accept it?

IDK. I understand the direction they decided to take.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by noobermin on Thursday June 30, 2022 @10:56PM (#31941747)
The issue with screen recording is not due to backwards compatibility
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by kaba0 on Friday July 01, 2022 @04:21AM (#31943764)
There is no issue with screen recording.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by lobocinza on Friday July 01, 2022 @07:58AM (#31945181)
There is. e.g. recording screen from Chromium doesn't work.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by kaba0 on Friday July 01, 2022 @08:01AM (#31945209)
It does for close to a year now with pipewire.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by NotEvil on Friday July 01, 2022 @11:07AM (#31947415)
Can confirm
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by imachine1980_ on Thursday June 30, 2022 @11:20PM (#31941925)
i try to learn x11, is hell, i realy try im tech savvy but god sake. is this problem difficult hell yea, but heavens x11 makes 10x more complex that should be.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by mbreese on Thursday June 30, 2022 @11:32PM (#31942002)
I mean, when your default use-case includes remote rendering of a GUI to clients, you're going to end up with a complex protocol. In the era of heavy servers and thin clients, it makes a lot of sense.

But when most (every?) computer includes some kind of GPU, local rendering makes the most sense -- especially when that's how your primary competitors work.

I don't know enough about Wayland vs X11 to make an informed statement, but I do appreciate that Wayland explicitly didn't try to include remote rendering. Let's just leave that up to other protocols (VNC/RDP/etc...). Now if we can just get one of those protocols to work on an individual application/window basis as opposed to the whole desktop.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by simcop2387 on Friday July 01, 2022 @12:35AM (#31942413)
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by ncmncm on Thursday June 30, 2022 @10:52PM (#31941707)
I tried Wayland, back when. Then spent the evening repairing my newly broken Debian configuration. I had my X back, by the end.

Now I donate monthly to Xorg release engineering.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by yjftsjthsd-h on Friday July 01, 2022 @12:04AM (#31942214)
> Now I donate monthly to Xorg release engineering.

Could you spare a link, so I can follow your example?

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by ncmncm on Friday July 01, 2022 @12:59AM (#31942566)
Now that I am at my desk...

https://www.patreon.com/p12tic

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by blibble on Thursday June 30, 2022 @11:33PM (#31942011)
on my bullseye machine I can have sway running on tty1 and Xorg/xfce running on tty2 (at the same time, same user)

(for when you very rarely need to use X)

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by Neeek on Friday July 01, 2022 @12:04AM (#31942215)
Not being able to have multi-DPI in X is what moved me over. Scaling one display makes everything fuzzy and increased my idle load substantially, though maybe a different compositor might have given different results.

EDIT: I should also mention that my experience is overall positive, I use swaywm so config and setup is easier than with X (no xorg.conf to tinker with every driver update) with a small stability tradeoff. Sometimes sessions will crash out when doing things with the GPU dmabuffers, which for a lot of people isn't really acceptable, but also who's usually using dmabuffers?

Oh and mouse interactions can be really wrong when going between xwayland windows and native ones.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by rickstanley on Friday July 01, 2022 @11:55AM (#31948267)
Looks like there is a plan to implement Wayland in Kfce: https://wiki.xfce.org/releng/wayland_roadmap
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by blibble on Thursday June 30, 2022 @09:59PM (#31941293)
sway is a drop-in replacement for i3 if you want to try again!

(and I think the nvidia issue is solved or close to being solved)

wayland has been the only way I've managed to get tear free smooth 60fps on Linux (trying intel, nvidia and amd drivers on Xorg)

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by linsomniac on Thursday June 30, 2022 @10:28PM (#31941512)
Agreed, I switched to Wayland and Sway when I upgraded to Ubuntu 22.04. It has basically been a drop in replacement and has been working great!
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by d3nj4l on Thursday June 30, 2022 @10:56PM (#31941741)
I've moved to using a mac as my primary device, so no more Sway or i3, unfortunately :'(

Though, fwiw, I had no issues with screen tearing once I started using picom. I used to have mild tearing before that, but after setting up picom (don't remember how I configured it exactly) I got buttery smooth output!

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by Jiocus on Friday July 01, 2022 @12:20AM (#31942317)
The relevant picom option would be:

    vsync = true
Love picom
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by aaronchall on Thursday June 30, 2022 @10:08PM (#31941362)
I'm using i3, specifically i3-gaps and I'm rather interested in switching.

I don't have nvidia.

Where can I learn more?

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by wezm on Thursday June 30, 2022 @10:25PM (#31941496)
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by wfleming on Thursday June 30, 2022 @10:30PM (#31941520)
The Arch wiki page for Sway is a pretty good starting point: https://wiki.archlinux.org/title/Sway#Configuration.

FWIW I was also an i3 user for a long time (and xmonad before that), and I’m a very happy convert to Sway.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by xfalcox on Thursday June 30, 2022 @10:50PM (#31941683)
There is a Manjaro Sway community flavor if you want to USB boot something preconfigured and check it out.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by unrealhoang on Friday July 01, 2022 @12:43AM (#31942471)
is the problem of blurry on XWayland for hidpi solved yet? That one prevented me from migration the last time (still keep sway installed but only login to i3).
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by kaba0 on Friday July 01, 2022 @04:26AM (#31943794)
Well, that is an X11 issue though. But I don’t know the current state of that
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by wmf on Thursday June 30, 2022 @10:44PM (#31941637)
Wayland seemed to languish at 90% complete for years. Wayland was on by default in Ubuntu 17.10, then off in 18.04, then back on in 21.04.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by vetinari on Friday July 01, 2022 @04:03AM (#31943662)
Ubuntu single-handedly delayed Wayland adoption by years.

They didn't switch to Wayland by default, because the apps weren't ready. The apps weren't ready, because they ran on current Ubuntu just fine, so why would they change. Chicken, egg.

Compare that to Apple macOS. Apple breaks macOS compatibility at the rate that GNOME can gush with envy. But the third parties are quick to update, without dragging their feet for years.

So if the signalling was, that Wayland is inevitable by release XX.YY, apps would be ready.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by fmajid on Friday July 01, 2022 @07:23PM (#31954333)
No one in the Linux community holds that kind of sway (pun intended). Even in the days of proprietary UNIX you had OpenLook vs CDE/Motif. Sometimes the Cathedral does things better.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by Gigachad on Thursday June 30, 2022 @11:38PM (#31942043)
I have been on Wayland since Fedora switched to it a few years ago. These days I have picked up a few workflows that just don't work on X11 so my opinion has changed to X11 not quite being ready for real use yet.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by em-bee on Friday July 01, 2022 @08:26AM (#31945473)
interesting, could you elaborate what that is? i am happy on wayland, but i haven't noticed any difference.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by zamadatix on Thursday June 30, 2022 @11:07PM (#31941824)
Nvidia isn't even a big issue anymore (the proprietary and open drivers both run gnome, plasma, and sway Wayland sessions pretty darn well now) I think there overall was just too big a lag between the "rah rah" and delivery on 95% of the promises so there was a bit of pushback.

I went looking for a video demoing the first statement and came across https://youtu.be/sdSFzZCgWp0. I'd find a better video but sometimes the worse video is too funny to pass up :).

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by rektide on Thursday June 30, 2022 @11:11PM (#31941851)
The problems don't change the fact that it's better & smarter & obvious, and honestly the problems here are... frequently misstated ("Wayland provides no capture APIs"... uhhhh what? this ticket is closed & resolved >2 years ago & webrtc for example works fine.). Leaving X to have a massive rats nest of drivers, and giving every app supreme access to the session, was a terrible situation, and Wayland is a reasonable, far lower surface-area alternative that's far more sensible & leaves far more responsibilities in the kernel's trusting hands.

This post projects an idea that there is a new resurgence of push-back & dislike, a failure to come into fruition, but personally I feel there's been a long continual & ongoing history of refusenik/can't-do attitude, like nearly all new technologies & especially sizable open source developments face. And success is widespread.

What I see as somewhat new is that the pace in Wayland protocol development has indeed really tapered off, with a large part of that slowness being chalk-up-able to (alas) internal obstructionism. A lot of innovations have been really hotly contested. Rather than independent innovation (which Wayland protocols make imminently possible), there's way more bickering in the various protocol proposals & less getting shit off the ground. There's absolutely a place for getting it right, but the clashes have gotten louder & bigger & it's sapping the energy in the room. Virtual input devices for example have been a shit show and a half, all kinds of hard work & valid proposals getting snubbed & shot down left & right, rudely. Some stuff has just been slow: global hotkeys for example.

Even still, I think far more of the problems in this gist relate more to apps that just aren't well maintained (alike your NV gpu that has been a bad actor on the scene), aren't well cared for. Others of these grievances are kind of small & non issues, or just paranoia (eg: conspiracy-theory freak-outs about client side decorations), some are indeed deeply technical sticking points Wayland hasn't specified it's way through yet (hotkeys again), some just seem... wrong (most Intel users don't experience terrible godforsaken tearing all the time?) but a lot of them are just slow apps not doing basic good. Yeah. It takes a long time to improve a vast vast vast vast ecosystem.

That said, it's really been about a year that Wayland has been shipping truly genuinely en-masse, so the visibility & noticeability of issues is much much much higher than it had been.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by hakfoo on Friday July 01, 2022 @12:01AM (#31942192)
I guess what I never understood about Wayland is how they managed to ignore some very obvious problems X11 had, and created brand-new ones.

The fact there was no default widget kit is the big one for me. If you're developing a new GUI in the early 2000s, "all the software looks native" is pretty near table stakes. Yeah, not doing so probably avoided a huge holy war, but surely the right thing to do would have been to do Xaw, GTK and Qt flavoured bindings atop some native widget set so you're at least 70% of the way there.

The movement from "window manager" to "compositor" is a huge scope creep. I'm going to admit that one of the things that drew me into Unix/Linux in the late '90s was the appeal of highly customized X11 desktops (i. e. Enlightenment v0.15).

Now, an X11 "window manager" is probably a within scope of one, or a small team, of moderately competent developers. I think one of the big old O'Reilly X11 reference books actually had a clumsy but functional example with line-by-line commentary. I like that I can run something fairly lightweight (FVWM, for example), instead of having to pull in most of the GNOME or KDE desktop incidentally because I want frames around my windows.

A Wayland-style compositor, on the other hand, seems to be a much higher barrier to entry. The whole "nVidia works, but only with the GNOME compositor" sort of stuff reads as a sign that there's way too much involved in there. I don't recall ever seeing "You have to use TWM because AfterStep won't work with your Trident 9440 video card" back in 1998. I wonder if it would have made more sense to go with a paired approach-- a single master compositor implementation, with the complicated and more hardware-sensitive stuff involved, and a pluggable window manager that spoke to it.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by wmf on Friday July 01, 2022 @12:14AM (#31942280)
The fact there was no default widget kit is the big one for me.

This wouldn't have worked. Different DEs will never ever ever agree on a common toolkit. If Wayland had a single official toolkit that means that today one DE (probably GNOME) would be using Wayland and every other DE would still be on Xorg (which is unmaintained).

The movement from "window manager" to "compositor" is a huge scope creep.

It's not. It's actually simpler and more reliable to implement window management inside the display server than using a separate process.

I wonder if it would have made more sense to go with a paired approach-- a single master compositor implementation, with the complicated and more hardware-sensitive stuff involved, and a pluggable window manager that spoke to it.

Agreed. Wayland probably could have done a better job of putting 99% of the code in libweston so that different compositors would only have to reimplement 1%.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by kaba0 on Friday July 01, 2022 @04:39AM (#31943865)
> Agreed. Wayland probably could have done a better job of putting 99% of the code in libweston so that different compositors would only have to reimplement 1%.

But at the same time that was meant as reference implementation, prone to quick changes and no promise of backwards compatibility. It could hinder their initial progress instead.

Wlroots is exactly that and has been available for quite some years now (with many niche wms building on it)

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by kaba0 on Friday July 01, 2022 @04:37AM (#31943851)
I don’t know why should a window manager care about frameworks, possibly besides window decorations, but that is unique to each one. What if I want a simple framebuffer on the screen? I believe wayland’s solution is much more minimalist and elegant, you get a rectangle and whatever you draw over it I’ll show. Frameworks are very complex beasts, very much outside the scope of a wm protocol.

And I very much don’t agree with the window manager compositor “feature creep”. If anything, the only reason it was easy to write for X11 is because X was a huge monolith doing things it really was not meant to, making you in essence write a window layout plugin. That’s why it was easy. But that just pushed (and worse, solidified) the complexity a layer beneath.

Wayland instead solves the complexity of its problem domain, not more, not less. You can still write a window manager plugin over wlroots for example with not much work, but writing a wayland implementation is not the same thing.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by halo37253 on Friday July 01, 2022 @09:35AM (#31946141)
X11 was designed for use as a remote session. Largely built for Unix, these Unix machines we largely accessed remotely. Local Machines were not as powerful as the mini computers of the time that would run the more heavy duty applications.

Honestly it really wasn't until SGI and NeXT did we see powerful mini computers on the desk running GUI applications in the 90s.

X11 is due for a replacement, but users just dont want to let go. Linux GUI based applications are still a small user base compared to the headless nature Linux normally gets used for.

For every 1 GNU GUI using Linux user, there are 100+ Linux installs that run completely headless. So the demand to move to Wayland is small.

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by rektide on Friday July 01, 2022 @12:54AM (#31942533)
> A Wayland-style compositor, on the other hand, seems to be a much higher barrier to entry. ... I don't recall ever seeing "You have to use TWM because AfterStep won't work with your Trident 9440 video card" back in 1998.

All in all, the basics of Wayland are a pretty tight package. https://wayland-book.com/ goes through the pieces, and it's not a super thick read. The system of passing around surfaces is comprehensible, tight, makes sense, and there is very little fluff or barriers here, imo.

Wayland has a common core, but absolutely I'd grant that the various protocols do indeed make it a much less tightly coupled thing, with different compositors having different sets of protocols they support. So yes, some apps that require advanced capabilities run much better in some compositors than others; the compositor choice matters. Sometimes there are multiple competing protocols for the same feature-sets, but usually/historically, wayland-protocols hammers stuff out reasonably quickly & most of this is a matter of time.

Still, this is often easier than the past, where apps would have to each test for extensions & have various fast/regular/fallback codepaths depending on available extensions; not necessarily a hindrance to the window-manager, but a bundle of complexity for everyone else trying to use X11 adequately. The Wayland common primitives, on the other hand, are fairly universally performant & well chosen.

Returning to complexity for window-manager/compositor, the situation is not unlike X11 itself, where yes, a simple window manager (or compositor) is possible to spin up relatively quickly, but where there is a sea of different standards to implement to do a good job. Window manager hints, extended window manager hints, and a plethora of other standards existed around X11 that were up to the window-manager to tackle, and implementing each of those took a lot of time too, if you wanted good support for all apps. Different Wayland compositors also have different support for different protocols, and those are a bit deeper rooted capabilities, less superficial than many of the X11 hints (which, if ignored, were less likely to impede use), but the idea is the same: real support to really be decent took work in X11, and it takes work in Wayland to implement a good suite of protocols here too.

Where I disagree highly is calling out the hardware here. Wayland is closely tied to kernel fundamentals; any reasonably supported video card will perform adequately under any competent/non-specialist compositor today. (Certainly some compositors could demand higher standards, such as some of the experimental compositors requiring Vulkan, but generally compositors have very similar, very common requirements.)

> I wonder if it would have made more sense to go with a paired approach-- a single master compositor implementation, with the complicated and more hardware-sensitive stuff involved, and a pluggable window manager that spoke to it.

I like where we are, where there are various toolkits/libraries for accelerated implementing. Wlroots, which underpins chiefly Sway (the i3 replacement), has given rise to a variety of other compositors, spanning the gamut from quick/fast/experimental to rich/deep/powerful. libwayland still defines some core ideas, if not compositing implementations, to speed development somewhat. Weston is still available as a reference compositor, although yes it's designed (more or less) to be forked & enhanced, not built to be preserved & built (extensibly) on top of. Wlroots & other alternative toolkits fill this need, & provide a diversity of ideas for how we might get going. Projects like Greenfield, the HTML5 compositor (https://github.com/udevbe/greenfield) demonstrate the diversity we get from not having a single common core technology, are possible because of this belief in protocol & standards over implementations, eased though implementations might be from promoting something like Weston to the one-and-only implementation.

> The whole "nVidia works, but only with the GNOME compositor" sort of stuff reads as a sign that there's way too much involved in there.

We can't look at a anti-plays-well-with-others entity like Nvidia to assess what is/isn't a good idea. Nvidia spent nearly a decade stomping their feet & demanding only their way was ok. The fact that Embedded OpenGL itself, what the rock their obstinacy was built around (EGLStreams), is quite heavily on the way out further should stress how foolish & self-centered this vendor has been. This discompatibility indicates nothing, is no sign, except an indicator of what kind of a company Nvidia is/was (one that obstructed any implementations of well known & common kernel constructs).

Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by noobermin on Thursday June 30, 2022 @10:44PM (#31941633)
At least for me it felt like Xorg as long as it had been felt broken, and we saw those blogposts back then about it and were somewhat optimistic it would be a good fix. As usual though, it didn't really work out and years later things are still broken.
Re:Wayland is not ready as a 1:1 compatible Xorg replacement... by neurostimulant on Friday July 01, 2022 @05:59AM (#31944347)
Now that we have pipewire, I don't have any major problem with wayland anymore and use it on both my laptop and desktop.