Hacker News Reader

Comment by Fnoord | Hacker News Reader

It depends. For me this is about being future proof.

Its more secure than X, but you can compartmentalise as well via VMs (Qubes does this) or Docker (Jessie Frazelle runs everything in Docker).

Enlightenment [1] supports Wayland since E20.

If you use i3 right now, you can use Sway [2] as drop-in replacement. That's my plan (since I use i3) if I might some time.

SailfishOS [3] also already uses Wayland. Tizen apparently does as well. SailfishOS doesn't use profiling or ads, and has an Android compatibility layer.

KDE and Gnome might as well (according to [4] they do); I don't use those.

[1] https://en.wikipedia.org/wiki/Enlightenment_(software)

[2] http://swaywm.org

[3] https://en.wikipedia.org/wiki/Sailfish_OS

[4] https://en.wikipedia.org/wiki/List_of_display_servers#Waylan...

View on HN

What if my wm does not support wayland?

If it provides more security (I guess applications cannot draw over other applications, nor grab keyboard input unless they're in focus), then how can I have a wm? How can I have a screensaver?

Is there any reason to use it if most of my applications are running in xwayland?

Less code runs as root than with X, since the server is far more lean.

There should be zero tearing or artifacts in Wayland, and the latency should be lower as well. Both due to passive compositing.

Screensavers are a pointless waste of energy. I'm not sure why you mention them.

In Wayland, WM/DE use IPC to communicate with each other; not X.

In theory you can run multiple XWayland servers to separate from each other. If security is a concern, Qubes might also be an option. And you're still more secure and better performance with Wayland plus some XWayland than with X.

I still don't see how it is more secure. If the WM can use IPC and tell wayland 'hey, I want to send this keystroke' or 'what were the keyboard inputs?' then why can't some malicious application do the same?

Can I run multiple wayland servers separate from each other? If not, then I still don't see how wm can prevent a random application from pretending to be a wm but actually being a keylogger.

The Wayland compositor does that kind of task, not the DE/WM like with X. That's why porting to Wayland isn't trivial. The server has many less lines of code leading to a lower attack surface, and lower latency or less tearing, and better HiDPI functionality.

Ubuntu 18.04 gnome shipped with the option, but if you select there's a 50% of forming a black hole where your machine used to be.

I'm joking, but it really is super beta.

Wayland (with Gnome) is fine as a daily driver on Arch (I've been using it for months, since AMD drivers were mainlined). I guess Ubuntu's packages are just too old.

Wayland worked really well on Ubuntu 18.04 for the period of time I tried it.

Ubuntu uses Mir, developed in-house. Why, I don't know.

Reply on news.ycombinator.com