Sway has other problems, like null pointer crashes, crashing based on weird layout bugs. I'm still suffering from a bug which makes the clipboard on Firefox jus

Sway has other problems, like null pointer crashes, crashing based on weird layout bugs. I'm still suffering from a bug which makes the clipboard on Firefox just hang, perpetually. This is Firefox with the wayland backend enabled, which I had to switch to because the Xwayland backend would crash the entirety of sway in some weird resizing edge case. Sway is still unstable. Even if the bugs have gotten less frequent, having it crash is not an uncommon experience. And because they tied its feature set to i3, the scripting experience is really not great. I say all of this as someone who has: - used i3 for many years daily - used sway for many years daily - written both a Rust (https://github.com/norcalli/ksway https://github.com/norcalli/ksway) and Lua package (https://github.com/norcalli/lua-sway https://github.com/norcalli/lua-sway) for sway. - written about a dozen or more scripts for sway - contributed patches to Sway The bugs are so irritating and wayland is so irritating that it's driven me to have already started making both my own browser due to firefox's issues, and my own alternative compositor. I'd rather make something outside of both wayland and X that only runs programs that I personally wrote and have QEMU as an escape hatch than use either of them full time. And one day I'll port it to Raspberry Pi on a unikernel or just off of the bare ISA. E: Oh yeah and screen capture, IME, and various other things are still basically experimental.