That’s great news. A lot better than last time I tried to make it work.

Good to know!

I don’t doubt it, but do you happen to have a source?

The only plus side I guess is I only use that computer for a bit of gaming and not for anything else, and i did manage to turn of automatic updates before they AI-ified everything. If I had more time and energy in my day I’d dual boot it, maybe some day.

The vibe I’ve been getting lately looking at Steam’s push for Steam OS compatibility is that it might actually be worth trying a dual boot again next time I can bestir myself to mess with it. I’ve got W11 but managed to disable auto updates so I haven’t received all the AI crap, but also means my OS is increasingly behind on security updates, which I’m not pleased about.

I don’t care about the latest and greatest either, generally, so maybe even more worth it…although most of my new game purchases are indie titles and most of those only release for windows. So we’ll see. I already have a strong preference for Mac support so I can play stuff on my laptop too.

Not arguing with your choice (props actually, I respect the switch) but it is possible to get a legit grey market key for w11 Pro for a lot less. I think I got mine for $20-30 in early 2024?

Edit: I should have noticed I was in the Linux group before I posted that, I thought I was still in the gaming one I guess! Not advocating windows to anyone, it’s a terrible OS. But some people might need it for some things so I figured I’d share information that might help someone save a bit of money if they did. (Yes, there are other ways around that.)

Writing the tests first also ensures that the test actually fails when you expect it to. I’ve seen test suites that were silently failing for years because they were (presumably) written after the fact and people just assumed that they tested what they said they did. Went in for some other clean up, stared at the test for 10 minutes wondering “how did this ever pass”, and then came to realize that test assertions in Jest inside a forEach apparently don’t run in the context of the test and failures won’t make the test fail. Changing the forEach to a for…of made it all fail immediately.