3 ms·
At one point you need to have an understanding of what you're dealing with: you need to know of what type a value is. If we agree with this then why is it so c
by cageface 14y ago
At one point you need to have an understanding of what you're dealing with: you need to know of what type a value is.
If we agree with this then why is it so controversial to assert that types are also useful at the language level? For me working in a dynamically typed language is just as awkward as working with a schema-free datastore. Writing code is hard. Why not let the compiler help you?
- marcosdumay 14y agoTyped languages add a ton of boiterplate to what would be simple operations. That slows you down, more than most people notice. Now, that said, explicity typing makes it easier to catch a lot of mistakes, and helps you keeping you data consistent. It's very usefull... But slows you down. As a conclusion, you want to explicitly type anything that is important, but also wants to keep the explictly typed data to a minimum. (What makes optional typing, like in Haskel very interesting.) And, in nearly all the applications all the important data (and very little unimportant data) goes to the DB.