I find claims that static typing has no benefits just as ridiculous as claims that it has no costs. A simple matter of taste, nothing more.

Jun 9, 2014 · 11:50 AM UTC

7
3
2
Replying to @stilkov
@stilkov I’d rather say trade-off. But taste plays a big role fore sure :-)
1
@pvblivs I thought about that. But a trade-off would suggest there’s a “right” answer depending on context. There’s no right or wrong.
1
@jnfrd Complexity, verbosity, barrier to entry, more restrictions, a feeling of less flexibility, the need to get everything right at once.
Replying to @stilkov
@stilkov and of context. Web Apps != nuclear reactor
1
@markusvoelter Agreed, wouldn’t want a nuclear reactor to be programmed in Ruby, nor Java. In fact I don’t want one in the first place :-)
1
Replying to @stilkov
@stilkov I never thought I'd see anyone claim it's "a simple matter of taste."
Replying to @stilkov
@stilkov @ijoyce Isn't it weird how everything has tradeoffs? It's almost like you want to pick tools whose strengths match your problem.
Replying to @ijoyce
@ijoyce Agreed. I find it funny that people choose Node.js for the "performance" that one day they "might need".
Replying to @ijoyce
@ijoyce Not that Node is a bad choice. But choosing it for performance is a bad reason for choosing it.
Replying to @stilkov
@stilkov @ijoyce It's a matter of making the right trade-offs for your problem space. Taste shouldn't be part of the equation, though it is
1