My last week has been filled with Marvels Midnight Suns. XCom meets deck builder meets dating simulator-lite. I’m having a blast, considering none of those genres are my forte

That’s a fair point. I’ve always assumed it was a form of rate-limiting, but you’re right, that’ll be part of their analytics at least

I don’t hate YAML, but it has the same issues languages like PHP and JS introduce…there are unexpected corner cases that only exist because the designer wanted the language to be “friendly”

https://www.bram.us/2022/01/11/yaml-the-norway-problem/

Yes, testing infrastructure is being put in place and some low-hanging fruit bugs have already been squashed. This bodes well, but it’s still early days, and I imagine not a lot of GIL-less production deployments are out there yet - where the real showstoppers will potentially live.

I’m tenatively optimistic, but threading bugs are sometimes hard to catch

I’m curious to see how this whole thing shakes out. Like, will removing the GIL be an uphill battle that everyone regrets even suggesting?Will it be so easy, we wonder why we didn’t do it years ago? Or, most likely, somewhere in the middle?

Everytime I’m on a flight with infotainment, I wonder about the company responsible for writing the software. A small part of me wants to get a job at one of those companies, just to see what the process is like…

I kinda feel your pain. A project that I helped launch is written in Typescript technically, but the actual on-the-ground developers were averse to using type safety, so any is used everywhere. So, it becomes worst of both worlds, and the code is a mess (I don’t have authority in the project anymore, and wouldn’t touch it even if I could).

I’m also annoyed at some level because some of the devs are pretty junior, and I fear they are going to go forward thinking Typescript or type safety in general is bad, which hurts my type-safety-loving-soul