4 ms·
> But it certainly doesn't mean it's the better choice. If picking something else had the same cost, then you're absolutely right. But if implementing the prod
by pron 13y ago
> But it certainly doesn't mean it's the better choice.
If picking something else had the same cost, then you're absolutely right. But if implementing the production code is 6 months out of a 5 year project, even a language that is 10x more productive but takes 3 months to be proficient in (let alone to master), then it's just not worth it.
> I would say that when your problem is a one-of-a-kind, you'd rather think about the problem at hand and think of the implementation as little as possible.
Yes, but this line of reasoning may lead to Clojure, for example, in the application case and to, say, Java in the algorithm case. In the latter you play around in MATLAB for a long time; translating it later to Java is often a very technical process.