3 ms·
I started out in static, went to dynamic, and am now going back to static (this is not a rant about one vs the other). It is a change for sure. But how much di
by zer00eyz 11y ago
I started out in static, went to dynamic, and am now going back to static (this is not a rant about one vs the other).
It is a change for sure. But how much did you really let the complier catch before? You have already discovered the "rub" in dynamic languages.
The bit your missing is tooling. You really need to have a solid debugger, one that lets you step through the code. Most of the time this is going to be attached to a solid IDE, and thats also going to be of help!
There are places where TYPE will matter and you should still learn how to cast in your dynamic language of choice. The path from a local variable to JSON in a lot of dynamic languages is a good example, the int you have been using as a string might need to be cast an int to get it to behave the way you want it to, booleans may end up in this boat as well. A static language means the delta between running and RIGHT is pretty small, dynamic may mean this is fairly large. Sometimes it doesn't really matter, and you don't have to care, potentially saving you a lot of time.
What language are you coming from, and what are you going to!