Wayland support might be interesting, but Wine is pretty useless in *BSD. No one needs it and no one cares. They shouldn't waste time on that.
Instead, they should be making Sway work. Xorg will not be maintained anymore in the future, so Wayland needs higher priority.
>>6475 Wayland is a problem as a solution to a non-issue.
It's broken trash and as insecure or more than X. If that's going to be the case, let's just stick to X.
The main issue with BSDs nowadays is the lack of software. Even if they have software, it's horribly outdated. Even if it's horribly outdated, their package management is bad by design. In fact, there's barely any package management to begin with.
>>6493 >It's broken trash and as insecure or more than X.
Not true.
>let's just stick to X
Yeah, the biggest hole in UNIX-like systems. A piece of trash that remained the standard for 30 years. Sure, let's stick with it.
>lack of software
What software do you need that's not on the packages? Seriously, I can see all of them there.
>it's horribly outdated.
Not true (dunno about NetBSD, but OpenBSD and FreeBSD have updated packages).
>their package management is bad by design
While I agree with package management is not that great, it does work. In years using OpenBSD I only had issues with it while on using -current (this is normal, as -current is still under development).
https://www.phoronix.com/scan.php?page=news_item&px=NetBSD-Wayland-First-App
https://blog.netbsd.org/tnf/entry/gsoc_2019_report_implementation_of
https://blog.netbsd.org/tnf/entry/porting_wine_to_amd64_on1
Maybe nothing groundbreaking, but still I'm really excited.