9 ms·
> Static typing is not at all bad; usual static typing mechanisms are, due to the fact that most of them force you into designing your types before you even hav
by sbergot 7y ago
> Static typing is not at all bad; usual static typing mechanisms are, due to the fact that most of them force you into designing your types before you even have a working prototype.
> Typing is an invaluable tool of thought to help you understand your problem, yes, but it is just one more tool in the toolbox
For me those two sentences contradict each others. Types force you to draw an outline of your solution. For any non trivial problem this will be a time saver even in the prototype phase.
- tmcb 7y agoI can't see how they do, sorry. In fact, they complement each other. The usual static typing mechanisms I mentioned force you to approach a problem with their specific mindset, very much like math problems that add unreasonable constraints to their statements in order to check if you grasped a specific concept really well. In a real world scenario you should be able to reason your way out of the problem without such artificial constraints. So it should not be a restriction to anybody if they can accurately explain a concept or implement a program without using tools such as types.