←back to thread

Are We Wayland Yet?

(arewewaylandyet.com)
96 points picture | 3 comments | 07 Jul 22 22:22 UTC | HN request time: 0.001s | source
Show context
jpgvm ◴[07 Jul 22 23:14 UTC] No.32020896[source]▶
Ah yes. Nvidia. The green death.

At this point my systems are going to be pure AMD until status quo changes. I begrudgingly used Nvidia while they were the better of 2 proprietary blob options but now that AMD GPUs work out of the box with no hassle (for the ones I have tried at-least) and are competitive on performance for what I do (consumer workloads/gaming) then there is no contest.

Right now I'm daily driving Wayland + Sway on Arch and it's been mostly good. Only issues I have ran into have been weirdness in the whole Alsa + Pipewire + etc stack which is hairy AF. Configuring Electron things to use Ozone auto detection makes them run native rather than via XWayland which is nice too.

replies(5): >>32020938 #>>32020954 #>>32021123 #>>32021211 #>>32024717 #
1. doodlesdev ◴[07 Jul 22 23:18 UTC] No.32020938[source]▶
> Configuring Electron things to use Ozone auto detection makes them run native rather than via XWayland which is nice too.

How did you manage to set this up? Some environment variable? The best I've managed to do was to change the applications .desktop file to include Ozone wayland parameters.

replies(1): >>32021157 #
2. jpgvm ◴[07 Jul 22 23:43 UTC] No.32021157[source]▶
On Arch they tend to use flags files in `$HOME/.config` can generally just add `--ozone-platform=wayland` to force it to use Wayland.
replies(1): >>32021698 #
3. doubled112 ◴[08 Jul 22 00:54 UTC] No.32021698[source]▶
I had mixed results with the flags files.

At least the last time I tried, between Arch repos and AUR, I had some versions of Electron that'd pick it up, and some that wouldn't.