4 ms·
Tl;DR; some pattern in language X seems similar to language Y therefore X ~= Y . Argue why said pattern makes it hard to program in language X or Y, posit lang
by keithnz 7y ago
Tl;DR; some pattern in language X seems similar to language Y therefore X ~= Y . Argue why said pattern makes it hard to program in language X or Y, posit language A and B as saviors.
I find it hard to be charitable to these kind of articles. Not that I disagree with the problems expressed, or the advantages of certain languages making certain guarantees. Everything is a tradeoff, and I think you have to be very aware, contextually, what exactly are you leveraging in order to get a certain result. That extends beyond the product itself to things like lifetime, and human factors. I'd like to see these kind of articles more of the "Consider A || B given these kinds of conditions, beware, this may not be suitable for reasons H I J...".
- chriskrycho 7y agoI actually strongly agree with this. Notably the post doesn’t say anything about what you should choose in a given context. I’m in a context right now where I support a pure JS (not even TS yet!) app, and while a colleague and I occasionally joke about rewriting it in Elm, that’s literally a non-starter in reality (and all I’d never suggest it in reality!). Most of the comments here seem not to have grasped that the basic point of the post is that advances in programming language design—here, specifically around types—can make for real differences in your confidence when shipping. And that’s valuable! It’s also not the only value… but then, I never said it was, either.