Wayland set the Linux Desktop back by 10 years?

Re:Wayland set the Linux Desktop back by 10 years? by arikrahman on Thursday March 19, 2026 @09:56PM (#47449431)

I've had an interesting experience with creating a wayland compatability layer with Bitwig. Especially as I used Niri as the tiling window manager, it is even harder to use as a base as it less supportive of X11 compared to other WMs like hyprland.

This may be Niche, but DAWs are very rare to support linux, especially this stack. I would say it might be a stretch to say the company behind Bitwig is punishing Wayland users, I am sure they don't have the personnel for it, but it is a legitimate issue that companies will most likely be 10 years late to the new modernization into Wayland.

Anyways, I was able to configure it with a specific flake configuration. I had issues with third party windows, which was more of an issue with the floating nature of Niri, since Gnome with Wayland displayed external VSTs fine.

You can find my repository here if interested. It consists of a few files, and I made it easier to use with justfiles. https://github.com/ArikRahman/Nixwig

[ Parent | on HN ]

Re:Wayland set the Linux Desktop back by 10 years? by jmkr on Friday March 20, 2026 @12:00AM (#47450317)

Pretty much every vst, clap, etc plugin on Linux requires X calls because of how windows get created and then managed by the host.

I've moved to running Bitwig in an Ubuntu distrobox container. Hope you're enjoying 6, it seems they fixed a lot with the piano roll.

I had to set mouse warping off in my tiling manager for yabridge/wine plugins.

[ Parent | on HN ]