It's a bit of an over-generalization, though. Tech stack matters more and more, the larger a project gets, and the more people join it. Some languages and frameworks lend themselves better at long-term maintainability, as the code base gets larger. Other put so many foot-guns at your disposal, that you need a lot of discipline to keep things manageable. And, of course, once you start working together with others, the choice of language and framework becomes much more consequential, as it will limit who can join the project, how quickly they can become productive once they join, etc.
I promise not to knock it, but what was that stack? Thanks for sharing!
I agree. This is why, while I love knowing and messing around with other languages, I generally stick with Python unless I have a demonstrably good reason not to. (For web stuff specifically, Django is still my go-to.)
One good reason not to: I wanted to build something that cross-compiled to a single binary which could run on all major platforms, and benefited from a particularly heavy in-memory data structure so as not to burn through people's hard drives unnecessarily (though not much else). In that case I reached for Go, and ended up with https://github.com/hiAndrewQuinn/tsk powered by a big fat trie under the hood. Obviously tries aren't exactly groundbreaking technology, but Python's memory footprint would have made me uncomfortable, even if I did figure out how to ship it as a py2exe.