I think the term "Pythonistas" is more widely used

> you may need to question your choice of language if you start hitting performance ceilings.

Developers should also question if a "fast" language like Rust is really needed, if implementing a feature takes longer than it would in Python.

I don't like bloat in general, but sometimes it can be worth spinning up a few extra instances to get to market faster. If Python lets you implement a feature a month earlier, the new sales may even cover the additional infrastructure costs.

Once you reach a certain scale you may need to rewrite parts of your system anyway, because the assumptions you made are often wrong.