3 ms·
I usually find a lot more serious bugs in quick and dirty scripts, than in big systems, regardless of language. (Naturally, big systems have already survived th
by pas 9y ago
I usually find a lot more serious bugs in quick and dirty scripts, than in big systems, regardless of language. (Naturally, big systems have already survived the small PoC phase, plus usually big things are viewed as complex, whereas small scripts are dangerously innocent looking.) So in that way things like Ammonite (easy scripting using Scala) seem very useful - even if the runtime requirements are a lot heavier, than using bash (or python).
Furthermore, usually development uses type system as a tool, so it'd be hard to add typing when it's done. (I mean, usually functional doneness is checked or "asserted" in a large part through types, and unit/integration tests help with the rest.) So in this sense typing doesn't add more development time. It just makes problems a lot more explicit, so you know you're not done yet.
- galaxyLogic 9y agoExplicitly declared types are like anchors. They make it harder to change the program to be a different program. In many cases this is good since it tells whether a change breaks things or not. But it does add to the "mass" of your program, makes it harder to change its direction. Your declared types are the shared "language" under your program. It is much harder to change the language that what is said in it. Changing the language would actually change the MEANING of what has already been said.