In my opinion most interpreted languages today tend to produce very dense code. Fancy call chains and closures interleaving. If you look for a subtle bug those are hard to reason about, you have to know the details of a lot of different APIs.
replyGo is verbose partly for that reason, but a silly loop is a silly loop. The constraints are clear, you only have to do the logic.
[flagged]
reply> Python is a garbage language. Dynamic types are a disaster
replyPython has gradual type system.
We should all go back to writing assembly
replyNo we should write one of the many modern programming languages that handle certain projects way better, including kotlin, go, or Java. The only things python is best in class at are scripting and as a harness for high performance c++ or fortran.
replyWhat about the projects that python handles better?
replyI mentioned those explicitly. People are still using it as a backend language for projects like huge SaaS deployments though, with the hypothesis being that dev time is expensive. With modern languages like kotlin and go, I think that gap is much too narrow to justify using a slow and badly designed language with good syntax.
reply> X is a terrible language because of the lack of static analysis available.
reply> (Mocking) Yes, that's why we should go back to Y with even worse static analysis.
Sure