4 ms·
> What possible advantage is there to be gained from any other choice? If you're the only one writing the entire stack of code that gets bundled into the deliv
by jjav 4y ago
> What possible advantage is there to be gained from any other choice?
If you're the only one writing the entire stack of code that gets bundled into the delivered program, you're right, no real advantage from other choices.
But as that's rarely the case, there is a lot of advantage from having a forced type system. Otherwise your code might be great but you're pulling in libraries and code from many other teams who chose to omit type info and/or ignore all warnings so you still have the same problem.
- lliamander 4y ago> Otherwise your code might be great but you're pulling in libraries and code from many other teams who chose to omit type info and/or ignore all warnings so you still have the same problem. This is actually a really great argument. Having well-typed dependencies is a real benefit. But I would say you don't need to force typing on people to achieve that. In my experience with gradually typed languages (TypeScript and Erlang) you tend to see decent adoption of typing in prominent libraries. There are natural incentives (i.e. crashing software) that drive people away from depending upon libraries that don't have strong type guarantees.