4 ms·
> when benchmarking against strongly typed compiled languages, performance concerns become important, even if you have to write ugly code That seems to defeat
by ldh 14y ago
> when benchmarking against strongly typed compiled languages, performance concerns become important, even if you have to write ugly code
That seems to defeat the purpose of benchmarking to begin with, or at least makes it less useful for real-world comparison.
- just2n 14y agoIt's already not an apples to apples comparison. For instance, what's in the Node examples is much the use of frameworks built to enable rapid prototyping, not built to handle the needs of performance-oriented services. So we're comparing some optimized systems designed to be used in production versus frameworks designed to be terse instead of performant.
- ldh 14y agoThat's fair. Though I think anyone who just picks technologies based on these bar graphs alone is also missing the point, so some critical thinking is required to interpret these benchmarks, as usual.