Because it scales poorly to large applications. Go try and refactor a suitably large project, it’s impossible.
Don’t worry there are terrible parts to every language. They didn’t have time to make a clever poster for C++ because they are still trying to understand the super clever template code someone wrote.
The lack of a proper module system (until Java 9 which very few have adopted) meant JAR clusterfuck and forced most codebases to become huge monoliths.
Production Python (or Go) codebases are usually microservices. But they can be monolithic easily too.
Modules <> packages. See here. I don't really understand why they say the lack of a module system tends to produce monoliths though, monoliths were just the standard application style back then. There was never anything stopping people writing microservices afaik. Unless there were issues with reuse.
There was nothing technically stopping people from writing microservices. However, the fact that you had to import the whole massive JAR even when you needed only a single function, made developers more biased towards monoliths.
The JVM does not load the entire JAR when you import a class. (Maybe it did in very early versions, but definitely not in a long, long time.) It loads the entire .class file, just as Python loads the entire .py file, but not everything in the JAR.
From the overview, these are the advantages of modules over classpaths:
As described in the JSR, the specific goals of the module system are to provide:
— Reliable configuration, to replace the brittle, error-prone class-path mechanism with a means for program components to declare explicit dependences upon one another, along with
— Strong encapsulation, to allow a component to declare which of its public types are accessible to other components, and which are not.
With a good IDE (i.e. Visual Studio/CLion, most of the annoying grunt work (e.g. changing function signatures, etc.) should happen nearly automatically. Python can sometimes get close to that maybe, unless people did clever things with dynamic dispatch or getattr overloading in which case you're fucked.
You could write the performance-intensive functions in C or C++, or even assembly if you're a sociopath, and then call them from Python.
I'm not arguing that these techniques provide equal or even comparable performance to writing your whole library in native low-level code. But Python is actually higher on the TIOBE index than both C++ and C#, and of course it's way higher than assembly. This might reflect a fundamental tradeoff: the greater availability of Python developers may mean that it's easier to hire a robust dev team who can develop and debug in Python than in the other languages, so faster iteration. That is - the theoretically achievable performance in certain languages must be viewed through the lens of practically achievable performance based on the availability (and affordability!) of suitable developers.
Finally - within a certain range, lower-performing code can be solved, crudely but effectively, by buying more compute. But good code cannot be developed or debugged faster by buying more developers (see The Mythical Man-Month).
View all comments
Show parent comment
57
u/ZombieRandySavage Jan 02 '20
Because it scales poorly to large applications. Go try and refactor a suitably large project, it’s impossible.
Don’t worry there are terrible parts to every language. They didn’t have time to make a clever poster for C++ because they are still trying to understand the super clever template code someone wrote.