Sure X isn’t a hot mess unlike wayland… sure…
X has been tepid for at least a decade.
deleted by creator
But hey - Metro runs perfectly fine, that’s all I need.
As someone using Wayland I can confirm it’s indeed not a hot a mess
Okay, but that would have made a shitty joke wouldn’t it?
Hmm… I don’t know maybe it’s fine as a joke.
Can I use AwesomeWM, XMonad, or StumpWM on Wayland?
Can I run a GUI program over ssh?
Does it support the X selection and clipboard protocols?
(These are not rhetorical questions, I’m really asking.)
No you cannot run any of those WMs, some of those do have ports with varying degrees of completeness but only sway(i3) and hyprland(hypr) are ready for prime time.
Yes, using waypipe
Yes, primary selection does work along with Ctrl+c although as others have mentioned it forgets when the app you copied from gets closed
Can I use AwesomeWM, XMonad, or StumpWM on Wayland?
Can you run macos software on linux?
Can I run a GUI program over ssh?
This is more of a why would you… Although, waypipe
Does it support the X selection and clipboard protocols?
Too lazy to google, but overall clipboard works as expected, both C-c and text selection. I remember experiencing problems with clipboards in vim (like 2 yrs ago) which were fixed by switching to nvim
deleted by creator
Seconded. Although that very much depends on the compositor of choice: I’ve been trying out a few new shiny things (well, pinnacle, strata, buddaraysh), and they aren’t exactly usable rn. With the exception of the latter one, probably (since the author claims to use it), but I haven’t been able to start it so far… On the other hand, major players like hyprland and sway work perfectly fine on my machine :tm
I’m on KWin Wayland, it also works great. I actually never noticed that I was switched from X11 to Wayland when I reinstalled Debian.
I personally run sway. I was really looking forward to kiwmi but that project looks dead
OK cool. When will it support nVidia?
inb4 it’s nShitia who must support Wayland
Wayland compositors run entirely in userspace and do not interact directly with hardware drivers. If Wayland doesn’t work on nVidia but X does, it’s a Wayland problem.
Compositors do directly interact with the drivers though. The reason Wayland doesn’t work on Nvidia is because Wayland uses an API called GBM(generic buffer management) to draw directly to the Linux VT. The Nvidia drivers don’t implement that API, the API that both AMD and Intel drivers support. It very much IS an Nvidia problem and not the other way around. Nvidia tried to convince all the Wayland developers to use EGLStreams instead but no other drivers use(or even support) that API, everyone agreed on GBM except Nvidia. That’s not Wayland’s problem.
Iirc Nvidia also skipped the initial meetings that AMD and Intel attended, where it was decided they would move forward with GBM
Amusing video covering this topic https://www.youtube.com/watch?v=5VGMdLAKQ0c
😂 But X is a very old spaghetti code from the 80s and is a security nightmare. I use X, btw!
Third options?
TempleOS? Not sure if it runs X or not, but it sure is solid.
improvable, also wayland problem isn’t fundamental, is the slowness to merge new protocols, wlroots, for example, add protocols that aren’t approved in the wayland gitlab to make it work better, so… third option is wayland, with protocols waiting for approval(that can be updated later if the protocol changes idk)
also nvidia, but that can’t be fixed with a third option anyway
to be fair people need to read the gitlab discutions, the devs there aren’t approving protocol just because the sake of it, is really hard to make things work securely and on every plataform, also, there things that really don’t need a protocol to work, look at the QT handoff that fixes an issue that even on xorg wasn’t fixed, and without needing a new protocol
other than that, certaing things like the tearing could have being merged earlier lol
Windows…
Blasphemy! And also I’m poor, although I guess if I really wanted to run spyware as my kernel I could pirate it.
But yeah, I’m getting the sense those are the two games in town, Linux-wise.
The kernel is fine, it’s been in the hands of pretty cool people since at least NT. As for the stuff running on it, well… 😗🎶
Really? Is it open source, or are we just going by reputation of the developers?
I actually don’t know much about the kernel they use, I was really just trying to emphasise the level of trust you put in your OS.
Easy, because Cinnamon is on X. When Cinnamon is on Wayland, so will I (and when I don’t have an Nvidia GPU, I guess).
Same here. Sure, KDE and Gnome may have great Wayland support by now, but what about other DEs? The situation in XFCE seems to be pretty grim:
It is not clear yet which Xfce release will target a complete Xfce Wayland transition (or if such a transition will happen at all).
MATE seems to have piecemeal support. No idea what the status of LXDE/LXQT are. And there are plenty of other window managers that don’t have the manpower to support wayland either.
The deprecation of X is going to leave a lot of dead software in its wake.
Yeah, people like to pretend KDE and Gnome are the only options. I dislike both. Cinnamon is the (unintended?) spiritual successor to the last Gnome I liked, which is Gnome 2.
It’s very much intended. Cinnamon was forked from GNOME 3 when it was released. It was intended to preserve the old GNOME 2 layout, but ended up evolving into the Cinnamon we know today.
No Barrier for Wayland. :(
I actually quite like wayland
I too like my macros not working
Idk what the problem with you setup is but fir me every macro i have works. Be it programmed into my mouse or defined by my WM
Insert comment about the window icon protocol here
What about windows icon protocol ?
Apparently there’s a massive controversy over what should be an extremely minute detail
I’m confused, wayland.social is just another mastodon instance, yes? EDIT: Oh presumably it’s a joke
It’s a Linux joke. Basically, the X display server is an unmaintainable mess, so it is being phased out in favor of Wayland.
