Key point: they’re not threads, at least not in the traditional sense. That makes a huge difference under the hood.

Really? Huh, TIL. I guess I’ve just never run into a situation where that was the bottleneck.

Definitely not a guarantee, bad devs will still write bad code (and junior devs might want to let their seniors handle concurrency).

It’s safe to assume that any non-trivial program written in Go is multithreaded

You can also just tell GitHub to not do that.

Unless I have an external monitor, keyboard, and mouse, using an external keyboard with a laptop is a shitty experience for me. And if I’m at home and trying to get work done, I’m using my desktop PC.

That’s an artifact of JavaScript, not JSON. The JSON spec states that numbers are a sequence of digits with up to one decimal point. Implementations are not obligated to decode numbers as floating point. Go will happily decode into a 64-bit int, or into an arbitrary precision number.