Re:I am disappointed by dynamic typing
by ReflectedImage on Tuesday November 29, 2022 @07:21PM
(#33795275)
The 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?
How are the interfaces between these microservices defined? Without types? Lol
Re:I am disappointed by dynamic typing
by ReflectedImage on Wednesday November 30, 2022 @07:10AM
(#33799621)
The interfaces do have types (and also proper versioning) but the internal code to the microservices does not.
Re:I am disappointed by dynamic typing
by gruffle on Wednesday November 30, 2022 @02:43PM
(#33806482)
Think about that for another second and see if you can spot the obvious huge flaw there.
Re:I am disappointed by dynamic typing
by ReflectedImage on Thursday December 01, 2022 @08:39AM
(#33816054)
I think you will be disappointed with the basic types: int, str, bool being used in one line per 1000 lines of code.
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.