5 ms·
It's a trade off. You don't want to write all your types for quick scripts, data analysis and small web sites. As a trainer, experience teaches me that it's al
by BiteCode_dev 6y ago
It's a trade off. You don't want to write all your types for quick scripts, data analysis and small web sites.
As a trainer, experience teaches me that it's also much easier for beginners.
Now, types are nice to have for bigger code bases, but that doesn't mean there is no place for a language with optional typing.
- smlckz 6y agoThere is Hindley-Milner type inference. Don't need to type types in most cases. See, for example, OCaml.
- wool_gather 6y agoThat comes with its own tradeoffs: increased compile time and more effort needed to create error messages that are helpful to the user.
- jgwil2 6y ago> more effort needed to create error messages that are helpful to the user. Well, sure, but that's a tradeoff for the developers of the language to consider. As a user, there are already plenty of statically typed languages to choose from with many person-hours put into just that.
- erik_seaberg 6y agoI want to offload as much work as we possibly can to the compiler. My brain will always be millions of times slower.
- GeorgeWBasic 6y agoOcaml is probably the fastest compiling language I've ever used.
- rscho 6y agoType inference does not mean untyped. Arguably, getting a type error when you didn't write a single type hint makes things even more confusing if you are not an experienced programmer.
- dan_quixote 6y agoIs it really that burdensome for novice programmers? Maybe it's just been too long for me to remember the pains...but I'd expect most novices to heavily use primitive types which shouldn't be that hard to grok.