You're right about python being the same. Python doesn't have a mature alternative to Typescript that launches it into having best-in-class type handling.

There's so much that my C# devs can't do with its horrible type system that Typescript "just does better". At compile-time at least.

I used to work on a hybrid typescript/python product (some services js, some TS, some python), and the TS stuff was just faster-running, easier to iterate, and better. And story-point allocations consistently showed that for an excess of 20 devs working on those codebases.

As for pip/easy_install vs npm/yarn/pnpm... I'm curious what you think pip does well that yarn/npm doesn't? I'll say in my work experience there's more/better enterprise private repository/cache support for node modules than for python modules. Using npm security databases alongside "known good versioning" allows a team of even 100 developers to safely add libraries to projects with no fear of falling out of corporate compliance regulations. I've never seen that implemented with pip

pip is the bane of my existence

Also python IS loosely typed. take a str and you can reassign it to an int or whatever