3 ms·
What I meant was that Node is super fast for cranking out proof-of-concept stuff, and that was its big win. When it got down to trying to close the performance
by dsl 15y ago
What I meant was that Node is super fast for cranking out proof-of-concept stuff, and that was its big win. When it got down to trying to close the performance gap between Node and Go (an order of magnitude requests/sec) we sunk a lot more time into Node unfortunately.
- cageface 15y agoThat jibes with my intuitions after looking briefly at both of them. Node seems like it would be quick for quickly banging out prototypes but I can imagine that all the other metrics might tilt pretty quickly towards Go. I've recently rediscovered the joys of static typing so that alone inclines me much more toward go.