Not really. But that’s one of Rob Pikes rules [1], I think the intention is to write whatever is simplest and optimize later. The programmer doesn’t need to remember 100 rules about how memory is allocated in different situations.

[1] https://users.ece.utexas.edu/~adnan/pike.html

Is there anything specific you prefer moving from the pandas API to polars?

Uninformed bets should wash out as noise, and informed bettors should reverse uninformed moves so long as they are profitable.

The ecosystem and tooling are great, probably the best I've worked with. But the main reason I reach for Go is that it's got tiny mental overhead. There's a handful of language features so it becomes obvious what to use, so you can focus on the actual goal of the project.

There are some warts of course. Heavy IO code can be riddled with err checks (actually, why I find it a bit awkward for servers). Similarly the stdlib is quite verbose when doing file system manipulation, I may try https://github.com/chigopher/pathlib because Python's pathlib is by far my favourite interface.

What position is the US in if all their goods are manufactured abroad? What if the dollar stops being respected?

It might seem like every group will be the same, but all it takes is to bump into one or two people you get on with and then you can organise things separately, avoiding the inner group toxicity.