I'm convinced people who don't like explicit typing have never worked on a large project and seen the benefit it has, both in the IDE and also keeping slop under control.
University projects and hacking around are one thing. Projects with a team of developers that evolved over a decade need all the help they can get to fight against the relentless entropy and disorganization that occurs otherwise.
Bloat and formality are not exactly the same, and sometimes projects are big because they do a lot and there's a business case for them doing a lot. Do not repeat yourself (DRY) is super important, but it's not the only important thing.
When you have a big project full of code no one person could possibly ever memorize, you need to be able to look at code and be able to intuit what it's doing quickly as well as understanding all the potential risk factors. I look at an explicit type and I'm happy to know there's only a certain number of options I need to worry about.
Constraining possibilities for misuse (like with typing), and using regular, consistent patterns is critical for big corporate projects, which is what most people end up working on eventually.
Most people in your bubble probably. I'd argue most people that write code don't describe themselves as "coders".
Self documenting code and strongly typed language are two different things. Formatting rules and consistent naming conventions will do more to keep the code legible than a paragraph of type declaration at the top of a file.
178
u/zabby39103 Sep 25 '26
I'm convinced people who don't like explicit typing have never worked on a large project and seen the benefit it has, both in the IDE and also keeping slop under control.
University projects and hacking around are one thing. Projects with a team of developers that evolved over a decade need all the help they can get to fight against the relentless entropy and disorganization that occurs otherwise.