At the end of the day, all I really care about is consistency. It's annoying to switch between projects which use different branch names to describe the same thing.

That being said, this is a dumb reason to introduce inconsistency.

Absolutely crazy. I'll negotiate on your behalf next time; just give me 10% of what I save you.

> rewrite it in Golang

Totally, I'm a big fan of statically typed, compiled languages; especially when the codebase is large and/or there are a lot of contributors. I chose the Node example because I feel like it offers the same "ease-of-use" that draws people to Python.

> get to the point where your code only takes twice the time to write and 2% of the time (and memory) to run.

100%. Sometimes this matters, sometimes it doesn't, but if we're talking about "smart performance hacks" this is definitely a top contender.

I work on a Python project and I really wish that it supported multi-threading. If I rewrote it, I would prioritize that feature in the target language.

> explicit iteration over Numpy/Pandas data in a Python loop

Yeah, I get it. I see the same thing pretty often... The loop itself is slow in Python so you have APIs that do batch processing all in C. Eventually I think to myself, "All this glue code is really slowing down my C." haha

> Pip just has horrible internal architecture that can't be readily fixed because of all the legacy cruft.

Interesting... I didn't know that. So they should be able to get similar results in Python then?

> absolutely possible to completely trash performance by naively assuming

Yeah, of course we'd need a specific benchmark to compare results. It totally depends on the problem that you're trying to solve.