I think it’s amusing that that opinion is so common given how bad X is. Mac OS X was developed in the nineties and has a jank-free hardware-accelerated compositor. Windows vista also had one, as well as every windows version after that.
I am certain that I’m not the only end user who notices the difference between smooth animations on those other OSs and what you see on X.
Wayland may be incomplete but it’s obvious that it solves some of these issues.
It's usually a driver configuration issue if you have tearing.
None of these need to be animated and even if they are not animated they can be disconcertingly janky under X. Tearing is even worse/more obvious if screens are rotated into a portrait orientation.
Then why does every popular desktop/mobile OS/app have UI animations?
Playing a movie produces moving pictures on a monitor? Great!
Tearing? Without telling them, they'll hardly ever notice it.
Users might not consciously call out screen tearing but they absolutely can tell when something runs smoothly. Just look at the reviews for iPhone vs Android devices in the early days when Android felt more like X11 with jank, frame drops and redraw glitches.
Then look how much time and money year on year Google spent fighting that jank. Money well spent.
And the irony is, that early iOS used animations to hide latencies when changing application state. These animations were the cause, why it was considered so smooth.
Then having a tear-free desktop is going to be something you strive for.
I upgraded every part of my setup which I needed to, just in order to be able to run Wayland (via sway), and I have to say I absolutely think it's worth it.
The end result is, hopefully, less bugs, more security and more performance, however most people wouldn't care anyway (and I think most people doesn't care, for example Fedora uses Wayland by default).
For us using window managers like i3wm the history is different. However in i3wm I am very close to the X11 so there is almost no abstraction, this is why the transition is more painful.
i3 users have sway. Good for them. Now what about every other window manager?
the xmonad dev for example has stated it's flatly not possible to "refactor" the project to use wayland... which means i'm not using wayland.
I'll continue to use X because I don't find it very broken. That's a problem for you?
I do however have a problem when open source introduces dependencies on buggy software written by aggressive narcissists, so yeah, I'm in the anti-systemd camp, or, put myself there when it started hanging a bunch of my Debian machines at boot when they made the switch. Pulseaudio was similarly garbage.
For WMs, it is more uncommon since they're so coupled with X11 specifics that this makes porting harder. However I don't really think it is a problem, if you want to continue using your WM it is fine, it is not that X11 is going away either way.
I have tons of scripts that does specific things and are heavily coupled on how X11 works. I need to port them to Sway first.
it wasn't exactly a drop-in replacement for me, but with a bit of modification I was overall pretty pleased with it, and subjectively it did feel faster.
> - It's faster than Firefox.
> - It's safer than every other browser out there.
> How do they get people to use it > Those two are not enough. To the user
If Mozilla wanted to take the route of switching people from Firefox to a new browser, they would presumably do it by gradually stopping development of Firefox. This is basically the strategy that Microsoft is taking with Edge, with the obvious difference being that it's a browser that comes pre-installed on a common OS, although I'm not convinced that the strategy would need to be fundamentally different.
That being said, as sibling responses have noted, I think the strategy that Mozilla has been taking has been to just move over components into Firefox itself when they're ready. This has already been done with a few important components, and it seems to be working fairly well.
For it to take over it must be shipped by default by all major distros and people need to have time to upgrade after it becomes the default.
This means switching to Debian 10+, any recent Fedora, Ubuntu 20.04+.
Based on this one would expect the majority of users to be using it by 2025
Sway isn't i3 rewritten it's not even the same developers. I3wm is its own active project with their own developers that will continue indefinitely.
From what I remember, Wayland makes it easier to mix 4K and HD displays without pain.
As long as it implements X, I don't mind, but my understanding is that the change is a breaking one.
It seems Wayland isn't going to be the default in Ubuntu 20.04 LTS, but if it wasn't for the risk of Wayland I would be on the non-LTS releases. At least Guix exists now so staying on LTS (released every 2 years) isn't that bothersome in terms of easily avoiding out-of-date software.
Would you be willing to share that? Pretty please?
(1) They aren't going to go out of their way to switch from X11 to Wayland. Many users don't even know (or care) what those two things are. Or they do but they don't see the required effort as justified.
(2) Users also aren't going to out of their way to change the default that their Linux distribution supplies. Not unless there are issues that are bad enough to warrant expending that effort. If it defaults to X11, they'll use X11. If it defaults to Wayland, they'll use Wayland.
The major risk I see to Wayland adoption is if distros play it wrong and default to Wayland before it's ready for prime time. If that happens, then users will get a bad taste in their mouth, and their indifference will get replaced with a preference against Wayland. And it will be hard to erase that preference because even if you fix all the issues, they will still remember that time when they tried it and it caused them problems.
Fedora has been defaulting to Wayland for several releases now. RHEL 8 also defaults to Wayland.
However, these distributions are probably not used by users, who consider their spacebar heating critical to their workflow.
call it Firefox v100 and automatically update
Let's assume Mozilla finishes servo (their browser in Rust). Let's also assume:
- It's faster than Firefox.
- It's safer than every other browser out there.
How do they get people to use it? Those two are not enough. To the user:
- It's different.
- Firefox feels plenty safe.
This is a real problem and Mozilla faces it now. As a result, they're focusing on what they can do with servo which no browser has done before, like superb VR support. In short, they need features to gain users and they recognize that. Marginal gains are not enough to encourage an entire product switch.
Back to Wayland. Aside from the lack of screen tearing, what can we all agree are big wins for the user? I haven't tried it yet (for this reason), but everything I've read suggests that it could be safer, it could be faster, it could bring some more new features, but mostly it's the same shit.
The masses, and this definitely includes the GNU/Linux using masses, need more than the same shit to change because change is tough. They are going to need something killer from Wayland, or another competitor, before they give up on X.