What's Wayland's status on FreeBSD?

Just succinctly - what's Wayland's status on FreeBSD? How usable and stable is it? What are limitations?
The FreeBSD documentation has a chapter on Wayland, that's great, but how does it behave in practice?
 
The local Wayland expert is probably NapoleonWils0n, but I can say, using both dwl (a dwm substitute) and labwc (an openbox substitute), that it's quite good, at least for my use case. This is on two workstations, one with an NVidia card, and a Thinkpad laptop. The only limitation, if you could call it that, is that I need to start the seatd service before running it.
 
i can log to plasma-wayland session through SDDM, but once the screen locked it becomes unresponsive.
i have a ryzen 7-5700u and AMDGPU activated.
 
I gave up on Wayland on FreeBSD. Reason: it takes an unreasonably long time to figure out minor nastiness. It works, but I'm a pass.
 
Works perfectly on my cheap Chinese laptop with Intel XE graphics (+ an external monitor connected via HDMI), FreeBSD 14.3-RC1 (but it worked also in 14.2), using labwc + sfwbar + mako and so on. This is one my latest screenshots:

1749196037366-png.22833


Wayland on FreeBSD has been my daily driver since last January.
 

Attachments

  • 1749196037366.png
    1749196037366.png
    1.8 MB · Views: 935
I don't know if this is a good answer for you, but I have Xwayland, and I tried running Xbiff, a little program that let's you know if you have mail. It worked, but not as well as in X. In X, if I started X and there was email, it would show me. With Wayland, if I started dwl or labwc, and there was mail it wouldn't show it. But would show it as soon as I got nw mail. I only tried it once, so please understand that's very anecdotal.
 
Wayfire works for me with wayland. Had issues with plasma6 with wayland. My laptop has a weird dual intel and amd graphics cards, which has caused issues for me before. But works great with wayfire for me.
 
Wayland started because Xorg is too big and too old. Now after 17 years, Wayland is old, but after adding all bits and pieces to make it work as good as Xorg, the collective size of the entire Wayland ecosystem is nearly as bloated. So, time to replace Wayland too :))
 
Unfortunately, today I have Wayland on my second SSD as an experimental testing ground.
Considering the trends on this forum, I think that the Wayland ecosystem will not be actively promoted in the FreeBSD environment.
Yes, it works, something starts, there is good performance, but the software developers are in no hurry.
Adaptation of ready-made and primary products like LibreOffice is also very lame.
I think that we just need to abandon the concept of "bloat", as is customary in KDE Plasma.
Then, yes, there is a chance to get something that works well.
Unfortunately, I experienced in practice how deep this hole is.
Today, only KDE Neon has implemented the Wayland ecosystem better than anyone else. But this crap is impossible to use because of
systemd.
Ubuntu SwayRemik is worse. There are a lot of unfinished business + systemd again. SUSE and Fedora are better, but again, everything is the same: surveillance, interception of control over your PC, etc.
Rating 0.5/1 - this is my subjective assessment of the state of Wayland on FreeBSD today. Only 50% of the work has been done at best.
It is unlikely that anything progressive will happen in the near future.
Unless you fork Wayland, bring the basic software to a working state.
I read threads for 2012. For example, everything is still bad with your energy-saving modes, sleep, hypernations (especially on laptops).
It has not become radically better. Therefore, having FreeBSD on a laptop today is only a loss.
And closing the laptop lid, and then restoring the state through magic commands...
Guys, to hell with such progressive technologies.
This is just insanity. Or as someone here suggested increasing the speed of Wi-Fi by pushing drivers through layers of abstractions and virtualizations (there is such a topic, search for it if you are interested)...
For that, I would permanently block access to the Internet for such advisers.
Things are going badly everywhere so far. Even in Linux.

Here is a dialogue of a famous oldfag programmer Andrew Stolyarov (translation):
Starting with Trixie 13, UsrMerge will be performed in Debian and Devuan. The directories /bin, /sbin and /lib will become symbolic links to /usr/bin, /usr/sbin and /usr/lib.
Is it time to leave Debian and its forks, or is it necessary, and Debian just can't keep up with Ubuntu/Arch/Fedora/openSUSE/Alpine/...?
It's high time to leave.
This is understandable :-)
I asked the question to find out whether it is worth looking at distributions where this usr-merge has already been done. I do not have enough knowledge to understand for myself what this change actually affects, and the articles about it are exclusively laudatory.
I do not quite understand how this can be considered anything other than degradation.
The point is that /bin, /sbin and /lib are what the system cannot take off without, while /usr with everything under it is all kinds of application software.
For example, /usr can live on a network drive. And if the computer is completely diskless, it should usually have its own root, including /bin and /sbin, i.e. a copy is made from the network on the RAM disk, while /usr in all its huge mass is simply mounted.
In general, I don't know what kind of moral freaks pushed through this idiotic change and who do you have to be to praise it. A dumb newfag scum is a dumb newfag scum.
initramfs has no right to exist and never had any right to exist, as well as loadable kernel modules. The kernel should be monolithic and rebuilt with any change in the driver configuration, everything else is a lousy sieve. Another question is that once the kernel was built in half an hour on an i386 with eight, or something, megabytes of RAM, and now you can't build it in any acceptable time on all these multi-core atmosphere heaters.
Progress, damn it.
 
This wayland thing is like watching a slow-motion car crash. I think I'll stick with MacOS on the desktop tbh.
 
Back
Top