@swick Chromium Wayland support appeared not yesterday. And its development has been so slow because it required too much changes at once. Of course, stating that more braking changes means more work is "deranged".

@swick Of course, fully. That's why I am saying that Wayland already has a lot of breaking changes and not having SSDs only makes migration more difficult. And I am well aware of GNOME's position on that.

@swick Without this "embracing" they could have switched to Wayland several years ago. Not being able to ask the compositor for basic decorations is an unnecessary backward compatibility issue. Podman doesn't look like GNOME and still is on X11. With the same effort it could have been Wayland for at least a year.

@swick The most of the post is about fighting GNOME's absence of server side decorations 😀

@verdre I here is me running with swapoff. Using swap adds stutters and trashes the ssd.

@jorge Emacs had it for decades

@thibaultamartin @matrix @jsparber @gnome @postmarketOS @pabloyoyoista You should have included Rust on the list, so I could wear this T-shirt while entering Phoronix forums

@JadedBlueEyes This is literally how some of the pull requests look today at work. People vibe code; don't even look at the output; git push if the app works; ask for review/approvals; get annoyed, when you question why there are two identical files; pass your comments to the bot; push again without checking when it finishes; manager advises you to tame down your perfectionism; also asks why do you do less tickets than others.

@jmaris I would say the comparison reads exactly like C vs. Java.