https://www.phoronix.com/news/Qt-Wayland-Compositor-Restart
As I understand it, in Wayland all the necessary state lives client side, so a client is free to wait around and connect to a new compositor. The compositor might not place the windows exactly where they were before, but there is nothing architecturally that forces clients to crash if the compositor crashes.
A single crash of what? I have used a Wayland only system for a long time and application-level crashes certainly don't bring down other applications much less the whole desktop.
Both window manager and shell were historically extremely likely to crash, whereas the display server was very resilient (and the session script would restart the WM and shell as needed). I'm not sure how separate the shell is nowadays, but more than just the traditional duties of a WM have been embugged into the display server.
https://arcan-fe.com/2017/12/24/crash-resilient-wayland-comp...
The WM and Shell are far more likely to crash, which is it's completely fucking retarded to move any of their logic into the display server.
I've been using wayland on three computers for the last two or three years and haven't had a crash that could be attributed to wayland in like.. more than a year?
I've had mesa driver crash when running a particular game a few months ago that eventually got resolved by... updating mesa. I bet many people wrongly attribute that to wayland.
you are talking about things you do not know enough about
A crash of the wayland compositor does NOT mean a crash of your entire session, in fact it is more resilient than X11 in this way
Edit: oh, I guess swapping FreeBSD for Linux? Yeah nah, I don't know GP, but I suspect this isn't a reason for them to switch OS just to solve this.
I also like that I don't constantly have to learn new stuff like the new ip commands or systemd. It just works. Oh and ZFS on root as a first class citizen is amazing of course.
This! I didn't realize how much I wanted this. FreeBSD release base packages are stable but all the regular packages are super up to date. Plasma looks very updated and stable.
I've tried rolling distros like Opensuse Tumble and Manjaro but eventually if you don't update them regularly you get a huge change and often many things change/break. Had your bluetooth speakers working finally? Now that's gone!
On the other hand stable releases in linux distros also seem to fail. Didn't update your random Ubuntu server in the corner of the office for the last year? Well now the apt links are broken and down for the release so you can't update the current release so you can upgrade.
> I also like that I don't constantly have to learn new stuff like the new ip commands or systemd. It just works. Oh and ZFS on root as a first class citizen is amazing of course.
It's nice, many of the same basics I learned on freebsd 6 years ago all still magically work. ifconfig works even with ipv6. You learn two files and you can do most anything.
I'm definitely gonna consider Freebsd for embedded devices if I can as well. You dint need buildroot or yocto as it's already part of the BSDs.
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
nixpkgs-unstable.url = "github:NixOS/nixpkgs/nixos-unstable"
Until it hard crashed my machine after I opened discord in firefox. Konqueror crashed on opening.