4 ms·

Not really understanding the down votes (maybe the double question mark??), but oh well. This is a valid comment considering that the EC2 instance mentioned is

Not really understanding the down votes (maybe the double question mark??), but oh well. This is a valid comment considering that the EC2 instance mentioned is a 2 core box, and there is a possibly that the node implementation didn't take advantage of both cores. - Go has multi-core support out of the box - Node.js has to be shown a little love, and has limitations. But this would have been a great use-case for Cluster. If the Node implementation was using all cores, then I wouldn't have asked this question. As it stands I don't really know what we are comparing even with all the graphs. Also we are still missing a little info on how they handled the requests. When you have a endpoint on a node server that is not a simple one, it is best to queue those before handling them (yes a additional queue). This prevents the process from choking because it just opened up NNN requests to S3. Most developers are not working with hundreds of HEAVY requests a minute, but in Node.js this usually has to be handled with care, and does not work out of the box. But if you want to pick up a shinier hammer then Go for it.

justsumbody 10y ago
Why would I want to use a language that requires bolt-ons just for bare minimum acceptable performance, meanwhile dealing with callback/half-promise soup, no types, etc? Also, I strongly suspect that an app that has been refactored multiple times by people well versed in node.js is probably already doing something to leverage multi-core...
mrweasel 10y ago
>Not really understanding the down votes Personal opinion: Because comments like your original one are annoying as hell. They never fail to show up. Someone post an interesting article one how they solved a particular problem and someone always have to show up with these pointless comments. Not everyone will know about, in this case Cluster, and it's not relevant without an explanation. Article and blog posts about Go seems to attract comments like: You might like Rust/Elm/Elixir and "that problem could have been solved using X/Y/Z package or framework". More often than not it's missing the point, which often is people, with little or no Go experience are managing to solve really complex problems within very short time frames.

justsumbody 10y ago

Why would I want to use a language that requires bolt-ons just for bare minimum acceptable performance, meanwhile dealing with callback/half-promise soup, no types, etc? Also, I strongly suspect that an app that has been refactored multiple times by people well versed in node.js is probably already doing something to leverage multi-core...

mrweasel 10y ago

>Not really understanding the down votes Personal opinion: Because comments like your original one are annoying as hell. They never fail to show up. Someone post an interesting article one how they solved a particular problem and someone always have to show up with these pointless comments. Not everyone will know about, in this case Cluster, and it's not relevant without an explanation. Article and blog posts about Go seems to attract comments like: You might like Rust/Elm/Elixir and "that problem could have been solved using X/Y/Z package or framework". More often than not it's missing the point, which often is people, with little or no Go experience are managing to solve really complex problems within very short time frames.