4 ms·
We did some bake-offs with node and Go (and other languages of course). Go won pretty much across the board, except in the time to write category. The other bi
by dsl 15y ago
We did some bake-offs with node and Go (and other languages of course). Go won pretty much across the board, except in the time to write category.
The other big downside to Node is hiring. You have two types of "JavaScript" developers. People good with JQuery, and people who have written JavaScript books. There is extremely little middle ground from which to hire good to awesome developers.
Go is the C replacement.
Node.js is going to be a Ruby replacement one day.
- cageface 15y agoInteresting. My own limited experience with Go suggests that it requires more time to write but less time to test and debug and tune so it might b a wash overall. Where did you find you were spending most of your time?
- dsl 15y agoWhat 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.