FizzyOrange

Some bad interview questions are like that, sure. But they're supposed to be things you are very unlikely to have done before and can reasonably figure out. It's not too hard to come up with simple questions like that. (Though I will grant many people don't seem to bother.)

IMO this is not a helpful way to put it. They measure skill under stress. Stress may have a large effect on skill level for some people but highly unlikely that it's so large that performance is completely random.

You don't know how good you've got it. The hiring process in other industries is much worse.

On a university network.

Yeah me too but if you keep reading they didn't actually "move on" in the way that it sounds.

I agree, but if you take away the hard numbers from this (which you should) all you're left with is what we all already knew from experience: fast languages are more energy efficient, C, Rust, Go, Java etc. are fast; Python, Ruby etc. are super slow.

It doesn't add anything at all.

IMO it's not as good a language as Rust, so I wouldn't learn it for the purposes of making something. However it's very easy to learn (at least to a productive level), so you may as well if you want to.

Just work through go by example and see what you think.

By far the best thing about Go is the tooling. Language itself is eh.

Yeah you can use it for normal software. It is very complex though, and the documentation assumes you already have a PhD in formal verification.

Sure, but I don't think that's an excuse for things like global hotkeys not working.

It's a very heavily gamed benchmark. The most frequent issues I've seen are:

• Different uses of multi-threading - some submissions use it, some don't.
• Different algorithms for the same problem.
• Calling into C libraries to do the actual work. Lots of the Python submissions do this.

They've finally started labelling stupid submissions with "contentious" labels at least, but not when this study was done.

They chose an “optimized” set of algorithms from “The Computer Language Benchmarks Game” to produce results for well-optimized code in each language.

Honestly that's all you need to know to throw this paper away.

Stop linking this, please! Any benchmark where Typescript and JavaScript are different is trash.