I started working on Flyaway with the intention of becoming familiar with Wayland, its protocols and extensions, and the wlroots library. Instead, I ended up genuinely liking all three.

I started working on Flyaway with the intention of becoming familiar with Wayland, its protocols and extensions, and the wlroots library. Instead, I ended up genuinely liking all three.

  •  kixik   ( @kixik@lemmy.ml ) 
    13•1 year ago

    What I’m missing from wayland, it’s not really something from wayland itself. Examples are several needed electron based applications, which some will refuse to properly work (for meetings, desktop sharing, etc), wine, gtk4 applications not respecting GDK_DPI_SCALE (not sure if already addressed) when not using gnome (wayfire being used as compositor), no proper support for conky (or eventually equivalent wayland functionality) yet, and several nuances with waybar, and some other tools. Major issue is my work dependency over some non floss electron binary blobs, like teams, slack, and so on, which particularly for desktop sharing and meetings don’t yet work properly, no matter the electron options one can use for them, and some floss I use like signal, freetube, jitsi. Wine has a horrible hack, which I might live with, but it’s horrible…

    So I’ll have to wait further for non wayland stuff to truly support wayland, and it has taken ages for that to happen, :(

    I haven’t tried labwc, andit sounds interesting, though I don’t like openbox configs, and I really love fluxbox ways, which are also text files, but I never got used to openbox configs, perhaps just because I got way too familiar with fluxbox, which is what I use with Xorg (fluxbox + picom + tint2 + conky).