3 ms·
I feel like you can partly get around this by slowly increasing type specifically over time. With strong type checking the risk of refactoring is low.
by roland35 2y ago
I feel like you can partly get around this by slowly increasing type specifically over time. With strong type checking the risk of refactoring is low.
- taeric 2y agoCertainly, but that goes a bit against the idea of incredibly strong types that people often visualize in their mind. Irony being what it is, most strongly typed programs that I have been introduced to were incredibly tight knots that were not easy to refactor. Many of the restrictions in the types would be far too strong from what was needed by the program, and refactors grow in difficult to explain ways. This is all to say, the discourse here is fraught with nobody acknowledging that "well done" programs of near any paradigm/style are well done and work. Evidence is often used that languages that allow looser ideas are more numerous than those that don't. This ignores that lack of existing programs in the strongly typed world could also be lack of ability for many people to deliver using those practices at all. Which, in turn, ignores that that may be a trade off that is worthwhile in some industries. (I suspect it goes on.)