Perhaps X.org should sue Elon Musk over the whole X thing. Then when they win the lawsuit, use the money to build an even better X.org that rivals Wayland.
They're already building that. It's called Wayland.
Groundskeeper Willie meme
X companies are are natural enemies
Like X(org) and X(twitter)
Or X(org)and x(nxx)
Or X(org) and x(wayland)
Damn X, they've ruined X!
Nah, they do the same errors of Xorg in reverse.
You know who is developing Wayland, right?
Wayland is maintained by the same people who made X.org. If you like X.org maybe you could volunteer your time to do maintenance on it. No one wants to touch a dead codebase.
wayland is great, unfortunately: nvidia
Imagine using a so called modern windowing system that doesn't even support custom degree tilted monitors
Who need fractional scaling when you can make a space useless tilted monitor setup lol
I can't find the documentation for it, but I swear Hyprland supports custom degree tilting.
Imagine using a so called modern protocol that leaves you unable to change a WM in a DE
Who needs xorg bloat when you can make compositor devs reimplement it instead and bloat their own codebase lol
There isn't such thing as a WM under Wayland. There are only compositors which make up everything such as the WM, Effects compositor, io etc. To standardize things for smaller compositors things like wlroots exist. Creating a basic compositor using that is around 100 lines of code
Yeah, and that was my point: Wayland turns DEs into inflexible monoliths. You trade modularity, customisability, and stability for better scaling, high-end monitor support, and theoretical security.
The theoretical security part is what got me "huh 🤨" as well... like "ok, but all of this is planned... or in the works... or it should work... when does the "it does work" part kick in 🤨".
There are only compositors which make up everything such as the WM, Effects compositor, io etc.
That's the thing i don't like about Wayland.
Considering that there are infinitely scrolling compositors and non-rectangular compositors, I guess tilting a monitor should be a smaller problem.
I'll switch to Wayland once it becomes the default in the distro I happen to be using that month. Not before.
Ubuntu and Fedora both use it. Its just a matter of time.
As someone who was completely ignorant to x and wayland until recently, my only experience is my distro having a wayland and x combobox during login, and random things not working when I switch it to wayland. The only reason I know this option even exists is because wayland was on by default and random stuff didn't work. I'll happily switch to the new better tech once it stops breaking stuff like KDE Connect and random games.
I'm using GSConnect (a compatible reimplementation of KDE Connect for GNOME) on GNOME/Wayland and it works just fine
I use an app on my phone that lets me use it as a touchscreen and keyboard for my Linux media PC. I have no idea if it will ever (be able to) support Wayland.
KDE Connect works on Wayland and can do all of that. Should definitely be technically possible.
Jesys. Way to butcher a meme template.
Switched to Wayland recently. Went to go play MechWarrior 5 with some friends and my mouse didn't work properly in the game. Switched back to Xorg. No more problems.
Wayland is one of those things you use once and then always use. (Assuming your not on Nvidia)
Assuming:
X programs work fine under Xwayland for the most part
No good remote desktop's yet :(
Switch from gentoo to fedora recently and use wayland as the default with nvidia
Everythings works fine until i fire up some games. All the games have this weird screen flickering and screen tearing which render a black box and literally unplayable. Tried rebooting, upgrading, downgrading and no avail.
Then i tried to use Xorg and everythings fine.
Ita frustating tho
Nvidia doesn't work well with anything
This has been an issue since NVIDIA introduced alternating frames in the 545 driver. To fix this, explicit sync was recently merged into the Wayland protocol, now all it needs is the merge into Xwayland and the new NVIDIA driver that supports it, which is rumored to be released as a beta around May 15.
Until then, you either have to game on Xorg or use the 535 driver.
If you're on KDE Plasma 6, there's an option to enable screen tearing in fullscreen applications, turning that on seems to have fixed a similar problem I had.
Most of the issues people have mentioned with either only seem to exist on specific distros or only for a small number of people with weird configurations.
Also everyone says Nvidia and Wayland is bad but Nvidia on x was garbage last time I had an Nvidia card too. Among other issues, the GPU control panel was such a hot steaming point of sale and wouldn't save configs.
I love Wayland but I don’t love half my apps rendering as blurry when using my HiDPI screen. Wayland treating me good so far. I wanted to ride the poo poo on xorg train cause of Wayland’s snappiness and being modern but functionality is everything.
meanwhile me: wayland goes brrrr cause of ootb touchpad gestures on GNOME
Going brrr since 1984?
I have a small script to toggle the visibility of a window when I press a hotkey. Press once, it launches the app if it's not running, or unhides and raises the window if it is. Press again, it hides the window.
My distro recently switched KDE to Plasma 6 on Wayland, and of course the script stopped working. Researched how to make a Wayland equivalent. You can't. It's literally impossible to hide (or even minimize) windows from the command line.
The compositor will have to implement a CLI. Sway has an IPC socket and CLI just like i3 and I can use this to hide windows.
Untested partial solution that you may already have tried:
In the window manager's keyboard settings, create keybinds for raising and lowering windows.
Create a script that uses dotool, a third party tool which can send keyboard events and mouse movements, to call the previously configured keybinds.
Missing bit: Figuring out whether the window is raised or lowered to know which keybind to send.
The author of dotool says that they wrote it because ydotool (the alleged successor to xdotool, I assume), needs root and a background daemon. That said, the linked page seems to indicate that dotool also needs some permissions.
I'm not affiliated with either.
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.