Ooo damn that sounds exactly what I’d like to try.

On the other hand I feel like I’m too old for this shit. My system works fine, I understand everything, and things rarely break and never in an unrecoverable way.

Don’t think I haven’t tried that.

I also tried the debug menu, xkill using the window ID, … it’s immortal.

Tbf, thanks to X11 Linux isn’t safe from stuff like that.

When I use my VR glasses, Steam sometimes creates an uncloseable X window that isn’t attached to any process. I don’t think even killing XWayland gets rid of it.

It’s been great almost since I started using it.

I started using it exactly when 4.0 came out, because that’s when I started using Linux and I thought learning 3 didn’t make sense. But 4 only got stable around 4.4 I think. The problem was that 4.0 wasn’t intended to be for end users yet, but distributions didn’t realize that and packaged it right away.

KDE didn’t repeat that mistake. 5.0 was almost completely smooth sailing (some applications took a long time to port and looked ugly, that’s it), and 6.0 was completely seamless.

If I had to guess, probably variable refresh rate

Yeah and they actually added some usability in the form of that utility helping you debug what you’re doing. Pretty nice!

Relevant, maintained? Zero.

I haven’t found anything better than Whiskey. It reminds me of the finnicky Wine days before Proton, but so far the problems I encountered are purely cosmetic. Granted, I only tried pixely indie stuff.

I don’t, my personal machine runs Linux

It works OK. Steam itself is super sluggish under it.

Native Steam + Proton is just better.

Hey, nobody disputes that.

Doesn’t mean macOS has a comparable portfolio of games it runs. Proton just works better than crossover or Whiskey or whatever.

Huh, I found it to be so much easier to set up than nginx that I wrote the devs a little thank you message

That’s just completely wrong. Just try e.g. replacing the journald backend with the old text based syslog, and not only will you discover that is possible (which directly contradicts what you just said), it’s also easy!

The only thing I liked was arch’s pretty boot sequence … which I stared at for a while because SysV init was so slow.

systemd, not SystemD, or system d.

But yeah, wonderful talk!

Once git no longer depends on it, it’ll be gone from my system

Nah, gross. You need to set a bunch of global options to get sane behavior on errors.

Nushell is shaping up really really nicely, and it’ll actually stop executing if something fails! Even if that happens in a pipe! And it’s not super eager to convert between arrays and strings if you use the wrong cryptic rune.

You can theme plasma and turn the effects off. Why isn’t that exactly what you want?

You can update the whole base image. Vanilla OS and SteamOS have an A/B partition that holds the currently-in-use image and can also hold a to-be-used image.

Updating works by adding the to-be-used image, setting a configuration option that tells the system to boot that one, and on the next boot it’ll check if the new one is bootable, then either boot it and mark it as working, or boot into the old one and display an error about how out wasn’t able to boot into the new one.

There’s smart things going on like maybe hard linking files that didn’t change between the two images and therefore saving space and copying time.

The result is that you never have a broken system, but you can still frequently update the base image.

I feel like that has been superseded by Nix these days. Arch is now boring stable tech.