That's literally what I'm saying; It's fine as long as there wasn't any unwritten data in the cache when the machine crashes/suddenly loses power. RAID controllers have a battery backed write cache for this reason, because traditional RAID5/6 has the same issue.
BTRFS RAID5/6 is fine as long you don't run into a scenario where your machine crashes and there was still unwritten data in the cache. Also write performance sucks and scrubbing takes an eternity.
It's like the cyber zombie apocalypse happened and there are only a few fortified camps left, the fediverse being a federation of camps.
I have the same experience. I wrote a simple program with SDL2 to test a software renderer. All it does is create a window then go into an event loop and after each iteration it streams a framebuffer to a texture that gets displayed in the window. In the default mode (X11) my frame timings fluctuate a lot and for a while I tried to massage the code to get it stable because I was convinced that it was just my draw code. Then I eventually forced SDL2 to use Wayland and not only did the draw time per frame go down by 2ms but the fluctuations went away completely.
Anyone that thinks X11 is still superior probably runs on a laptop with a single screen.
It really does seem that way. I've dealt with many different multi-monitor setups on X11 and only ever had problems. For example, I have an AMD based setup with 3 monitors, 2 are average 1080p60 displays and the third has a higher refresh rate. On X11 this setup always has either screen tearing/flickering, unusually high CPU usage by the compositor or the refresh rate seems noticeably off and hot-plugging additional monitors makes things behave weird or even crash, especially when unplugging monitors. On setups with multiple monitors across multiple GPUs it's the same but worse. On Wayland it all just works without any problems, no matter the setup. Hot-plugging monitors on Wayland is very seamless. Even X11 software runs better for me on Wayland.
From what I understand it's basically like a "thin client" type of thing where the client loads the Kernel from local storage up to a certain point and then boots into a rootfs that is somewhere else on a remote server.
This isn't limited to JS. Too many times have I seen someone ask a question of how to do XYZ in language ABC where most of the replies were some form of "Just use this library bro" while not actually answering the question. And usually the library that's being suggested is some big monolith that implements a ton of shit that no one really uses.
I briefly played China: Mao's Legacy. The UI design is awful and the game doesn't do a good job at explaining the mechanics to you. But once you figure things out it can be addictive. I don't remember much of the story but I remember the game giving you a lot of choices for events. I haven't played any of their other games but they all look pretty similar in terms of gameplay.