3 ms·
> and of course nothing would run on BSDes A number of wayland compositors are available in at least freebsd and openbsd (haven't checked on netbsd and dragonf
by prmoustache 2mo ago
> and of course nothing would run on BSDes
A number of wayland compositors are available in at least freebsd and openbsd (haven't checked on netbsd and dragonflybsd). Wayland is only a protocol. Whoever wants to support it can.
- kelnos 2mo ago> Wayland is only a protocol. Whoever wants to support it can. I'm kinda tired of this line that I see everywhere. The bottom line is that most people develop for Linux, and don't consider the BSDs, and so things end up broken, or not working at all. The popular libraries for writing Wayland compositors consider Linux first, and BSD support is bolted on later. The end result is that it's just more work for everyone. X11 could have been fixed, it's just no one wanted to do so in time to head off the Wayland work. XLibre and Phoenix might have ended up working out if they'd been started 10-15 years ago, but Wayland has too much momentum now, for better or worse. (Source: I am a Wayland compositor maintainer who would love it if his stuff would work on the BSDs, but I don't have the time or energy to install a BSD and test and fix.)
- prmoustache 1mo ago> The popular libraries for writing Wayland compositors consider Linux first, and BSD support is bolted on later. BSD devs can fork/write libraries too if they choose to or decide to not implement wayland which is valid too. I din't see anyone complaining that xorg or xlibre is providing source that build and work for haiku, redox for example. My understanding is that both projects have to maintain their own patchsets to make it work.