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.

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

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.

Because they just have their own brain chemistry as the basis of it whereas the above comment clearly states:

Rust has proven empirically that the tradeoff between performance and safety doesn’t need to exist.

Which is truth. And it’s much easier to base a coherent argument on truth rather than vibes.

dbg!() for Rust users

He works on Linux where he controls the whole stack down to the metal and I love that for him, but other people have to call library code, and them debug that if it doesn’t work as they thought it would.

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.

You say that as if somebody was disputing that.

The distinction ceased to be meaningful the minute language servers got introduced.

Laptop tries to reboot for 5th update of the day

I can’t connect to the internet, Dave, I’m afraid I cannot allow you to start me up again

You try to ignore helpful tips from the guy next to you, pretending your headphones are still active.

You choke back tears as Windows had enough from your feeble attempts to boot and the power button stops doing anything.

Hatch is great. It’s easy to get started but I wouldn’t call it simple. Flit is simple, because it’s limited.

Hatch is complex enough to allow you to override everything, which makes it not simple, but also not complicated.

I agree, although it undersells hatch and has a title that made me roll my eyes. Very well researched, none of the usual hot takes and clichés.

You’re right, of you have compete freedom, do that. If the place you want or need to go to is most comfortably reachable via rattlesnake road, bring boots.

In other words, if you don’t think the wasm landscape is mature enough to build a web thing with it, you are stuck with JavaScript, but you don’t have to rawdog it. I haven’t run in a single weird thing like this in years of writing typescript with the help of its type system, ESLint and a formatter.

[citation needed]

Just use a formatter. It’ll show you that the second one is two statements:

1. {} (the empty block)
2. +[] coerce an empty array to a number: new Number(new Array())