> All scripting is application development. Having variation of application lifetimes, deployment circumstances, etc., does not at all represent any difference

> All scripting is application development. Having variation of application lifetimes, deployment circumstances, etc., does not at all represent any difference of kind in terms of reliance on third party APIs, shared abstraction layers, or the standard library. It is all just application development. In the same way that boiling pasta is cooking. > I strongly disagree that these different use cases imply different requirements, But a art major student and a haute cuisine chef have vastly different needs in the way their kitchen is setup. It just happens that Python serve the whole spectrum of user base. You are seeing this from the point of view of a programmer. There is a enormous quantify of Python coders that are not. They don't have an IDE. Don't know what an env var is. Are not able to install dependencies. And they chose Python because it doesn't force them to. > e.g. for separately versioned instances of the same standard library module. How to address it properly is a different issue, and requires indeed a debate. > Python is not unique in this at all. Oh, but it is. See my other comment on the matter: https://news.ycombinator.com/item?id=21898070 https://news.ycombinator.com/item?id=21898070 It's very long, don't want to write that again. > The exact same phenomenon has happened since virtually the dawn of C programming. No. Geographers don't casually code in C. Math teachers don't have to teach it everywhere. You cannot be productive in C after 7 days of dabbling with it. And hence there is a huge number of people that will never, ever use C, or any other language, but use Python. I wish people saying that would accompany me on my job, going from company to company all day long to witness what is really happening outside of the HN bubble. Remember, if you are on this site, you are very far from 80% of the Python coders. In fact, if you even spell "Haskell" correctly, you are in another dimension. No one would ever mention C after that. For many, Python is way closer to Excel. > The same thing is true for C++, Haskell, Java, Scala and many more language ecosystems. > It’s all just application development. Some people produce fast food. Some prepare a pick nick. Some make a banquets for a family of 30. It's all just cooking. I'm sorry, no, this is a misguided conclusion. Python is the only knife I know that is popular for almost all of this different use cases of cooking, but all this different types of cookers. It makes it a special case. A very special one.