News for hackers. Stuff that matters.
Re:The memory safety problem isn't bad coders by gowld on Tuesday February 12, 2019 @02:48PM (#19146842)
It seems strange to say that something (types) isn't worth anything more than nothing just because it isn't everything (complete documentation)
Re:The memory safety problem isn't bad coders by acdha on Tuesday February 12, 2019 @02:55PM (#19146911)
You should consider overhead and completeness. If people spend lots of time writing boilerplate and coding around the type system but aren't saving a corresponding amount of time, there's a fair cost to that, especially if this means end up writing different classes of bugs but not really fewer of them. (This is basically an enterprise Java bingo card)

There's a certain argument that this is the sign of an inadequate type system: you're getting the overhead but it's not rich enough to be self-documenting or provide really rich analysis tools.

Re:The memory safety problem isn't bad coders by yxhuvud on Tuesday February 12, 2019 @03:42PM (#19147297)
Types gain you some things, but there is an overhead, both of expressibility and of terseness. The costs (and gains for that matter) are different for different languages, and also different languages are used for different things, which make different trade-offs worthwhile.

This means that the trade-off Crystal give could be way better than the one Ruby gives, despite Ruby giving a better trade-off compared to Java (for some use cases). For other problems Rust, Go or C could give a better trade-off.

It is not a discussion about if types, all other things equal, are good or not. The reason behind this is simple: Not all other things are equal and not all type systems are equal.