Easy for simple code for middle schoolers. For grownups with large codebases to develop and maintain, it's not optimal. Yes, like the tiny puny baby middle-sch

Easy for simple code for middle schoolers. For grownups with large codebases to develop and maintain, it's not optimal. Yes, like the tiny puny baby middle-school children who built microscopic useless toy "programs" (not even worthy of the name) at Instagram, YouTube, Dropbox... What I really, really hate is the lack of static typechecking. Then don't use dynamically-typed languages. Not everyone shares your tastes, nor do they have to. And just as bad the fact it is impossible to encapsulate code. The more you write here, the more I think C# is a great language for you. And I don't dislike C#! But you want a nice statically-typed object-oriented language with data hiding. C# is an example of one. Python is not. And then the GIL!! I've written at length about how the existence of the GIL is the result of tradeoffs that seemed perfectly reasonable at the time (keeping in mind that Python is older than Java, and I suspect older than the average HN commenter). With 20/20 hindsight would a different approach have been better? Sure, but if they'd had the ability to see the future in enough detail, the folks who chose those tradeoffs probably would have bought lottery tickets instead of building Python.