hot_gril

Definitely don't want to store types as columns in a DB, especially because of the inevitable thing that qualifies as two different types. In this situation, I'd usually take the first one (nullable cols) without much consideration. The DB doesn't need an xor constraint, but it can if you really want. New cols can be added without much impact on existing data.

And if the info is non-scalar, it's either option 2 (nullable FK) or 5 (JSON), depending on whether or not other things join with fields inside it.

Idk about the internal affairs, I just really don't like Python for web backend kind of things. It's taking them way too long to sort out parallelism and packaging, while NodeJS got both right from the start and gracefully upgraded (no 2->3 mess).

Also I used Python way before JS, and I still like JS's syntax better. Especially not using whitespace for scope, which makes even less sense in a scripting language since it's hard to type that into a REPL.

Aside from iTunes getting gimped, I don't feel like the Mac is neglected at all. Was annoyed about the 2016-2019 MBPs though.

Yeah, going from Intel to M1 was a huge improvement, but not in every way. So now they're closing all the other gaps, and it's getting even better.

Mostly, I trust the card that supports my software with the least issues.

There's nothing annoying about Nvidia cards though, unless of course you're using Linux.

Probably called that because it's smaller than the transaction of buying the game

What's the front door, WebUSB or something else like TLS 1.2?

localhost-only access is a reasonable compromise

In this case, it's probably because the alternatives are good enough, even if it's just that Firefox users open Chrome in specific instances where they want to connect to special hardware.

In a cross-platform way, kinda yeah. Especially on the Mac side where OS updates always break everything.

At least I'm a little relieved that Firefox and Safari don't support that either.