The Sway implementation (not Wayland as some DEs seem to run really smoothly) sadly is still completely hit or miss depending on your exact hardware setup. I have two device (both even with nvidia grphics *sigh*) and one of them is just a buggy and flickering mess.
X’ architecture is insecure. There’s no isolation between windows, and each process can spy on your input. That’s just one example.
Wayland is necessary.
Let’s do it right here!
Sway is a Wayland i3 implementation and you really should be using Wayland instead of X.
The Sway implementation (not Wayland as some DEs seem to run really smoothly) sadly is still completely hit or miss depending on your exact hardware setup. I have two device (both even with nvidia grphics *sigh*) and one of them is just a buggy and flickering mess.
Sway devs don’t support NVIDIA graphics
No, you only should be using Wayland if you need some of it’s features. If you don’t need mixed refresh rate/mixed scaling you’re fine using X.
X’ architecture is insecure. There’s no isolation between windows, and each process can spy on your input. That’s just one example.
Wayland is necessary.
Yet no known active exploits use this insecure architecture to cause actual harm. It’s just another FUD.
I’d hardly call that an exploit. There’s no protection.