3 ms·
What you are saying all breaks down with larger codebases. A codebase with 1000 people working on it benefits dramatically from static typing. Everyone who has
by twblalock 4y ago
What you are saying all breaks down with larger codebases.
A codebase with 1000 people working on it benefits dramatically from static typing. Everyone who has tried to do the same thing with dynamic typing has learned that. And quite a few companies that started off with Python had to rewrite everything in Java.
If you honestly think that nobody ever passes the wrong type, you've never worked on a complex dynamic codebase with a lot of people. It happens all the time.
- ReflectedImage 4y agoThe more modern solution is to break the large codebases into self contained microservices. In which case dynamic typing scales indefinitely. I've worked on dynamically typed codebases for a long time. Passing the wrong type is very rare. I mean how would the code pass the unit tests if it was passing the wrong type?
- gruffle 4y agoHow are the interfaces between these microservices defined? Without types? Lol
- ReflectedImage 4y agoThe interfaces do have types (and also proper versioning) but the internal code to the microservices does not.
- gruffle 4y agoThink about that for another second and see if you can spot the obvious huge flaw there.
- ReflectedImage 4y agoI think you will be disappointed with the basic types: int, str, bool being used in one line per 1000 lines of code.