I'd argue it hasn't even been fully resolved, progress has only just been made. Because the wayland devotees are too ideologically stubborn to acknowledge genuine concerns to treat these sort of problems with the attention they deserve, it doesn't speak well for Wayland in the longer future.
Not really a good analogy imo. Wayland wasn't delayed because of marketing it was because of autism. These are low level devs who like abstract concepts and didnt want to actually focus on implementation. They lacked the foresight to realize they actually needed a solid implementation to make a functional piece of software (such a difficult concept, I know).
Wayland has reached too much of a critical mass for serious issues to be left unattended. There's a reason Valve had devs forcing through changes needed for the Steam Deck
It was developed by the kind of people who used Sun Workstations back in the late '80s (and that is where I first encountered it and thought it was better than even Apple computers of the time). It wasn't developed for them, but those old Suns often had enormous monitors and just being able to have multiple windows open and keep track of all of them simultaneously was incredible.
Let's just say I don't hate it and it works and change causes me to start autistically screeching.
Kind've the exact point I was making. Perhaps it would've been better to say that few people love or are passionate about X. Its not a highly affectionate relationship with X, its impartiality and a dislike for instability and change. With the current trajectory X will be a minority platform and Wayland will be the solution supported going forward. If, 5 years down the line, everything you're looking for works well on Wayland, and a lack of support for X starts causing issues to arise with your actual software, are you going to keep fighting with your OS daily to keep using X? I expect this is how it will go down as applications from lazy developers stop supporting X because Ubuntu and Fedora have stopped supporting it. That was one of the bigger hurdles Wayland ran into as a minority in the market, and as the marketshare flips, so will the support.
5 years down the line - assuming they've addressed things like primary monitors by then - I'm sure I'll happily switch. Right now they haven't, So I'm going to stick with something that I know works.
EXWM is called the 'Emacs X Windows Manager,'' but if that changes to the EWC 'Emacs Wayland Compositor' then maybe.
you should really be calling it wlroots/Wayland because without wlroots wayland would be nothing.
sure, but don't apps and desktops also need to support it? several desktop environments are already talking about switching exclusively to wayland, because (understandably) developers don't want to upkeep two versions of these already massive projects. and i cant imagine random internet projects made by 1 person in their free time want to do the same. i've already seen programs i want to use outright REQUIRE wayland, and refuse supporting x11.
My dad had a NeXT from like ’92, and that thing had crisper graphics than Windows up to like 2005 or something. Display PostScript really was a marvellous thing.
I have nothing against Xlibre - I just dont see it gaining any momentum or mattering in the long term. I think it may offer some value as a temporary holdover for any issues people still have with Wayland, but the inevitable end result is that software is going to stop supporting X eventually and moving over will be the practical choice.
I think a decent amount of distros will either adopt it or get 3rd party repos:
I think we're just going to see more advanced and mature versions of shit like this (the opposite of xwayland):
So all of the people that are actually mad about wayland.
not that I've seen. It does force vsync basically. So you don't have screen tearing. but it doesn't require anything more powerful than running xorg does. Really if you run xlibre it's going to be doing the same thing. Or running xorg with it set to not allow screen tearing in the config. Really the only time I've actually ran into a situation where I would say it was heavily taxing on system resources. Was running xorg with picom, with certain configuration options set. I would really notice that.
idk. I'm someone that doesn't like systemd, but I just don't get the autistic rage over wayland. I couldn't care less if distros are using wayland by default or not. For one thing. it's way harder for a normal users to manually swap out the init system. Without having a good bit of knowledge about how things are actually working. So having a distro built around just the idea of having another init kind of makes sense. It's pretty easy to just install xorg, even if a distro doesn't offer it by default. And use that instead.
I'd like to interject for a moment...
Moreso, I think. I view systemd with distaste because it's goddamn hydra, and I'd like to get rid of it if that's an easy option, but it's not a hill I'm willing to die on. Of all the gripes I have with Manjaro *waves at a towering stack of boxfiles* systemd isn't actually one of them: At least it fucking works.
Quite possibly. But if we don't have retards like Sebastian Wick killing X11/Xlibre for religious reasons, that can happen organically if/when wayland is good enough:
You are indeed retarded.
The "anti-systemd revolt" never really amounted to anything, did it? I use Devuan, but I'm under no illusion that it's anything but a schizo distro just like all the other systemd-less distros.
