[imanaccount247]

>I'm a fan of NodeJS, but I would never use it to try to solve a computation heavy problem, it's good at IO multiplexing

No it isn't. It is very bad at it. It just uses the most primitive event loop and foists all the complexity of that onto you as the developer using it.

[Ixiaus]

You're being downvoted but you're right.

[BuckRogers]

He is, and I'm seeing more of this on HN over time. Many people who use <technology x> see a bothersome comment, and while snide- he was accurate. People may use Node.js, drank the Kool-Aid, but in 5 years there's going to be an industry movement off of it and the messes being created today. I've used it, was not impressed by its technical merits, and wrote it off as yet more technological churn.

I'm not a fan of churn, and keep a keen eye eye out for true innovation. Which happens far less than people are convinced to believe. That's the biggest scam the tech world convinced everyone, that innovation is rampant and fast moving, when in reality everything moves at glacial pace.

I'm a late adopter of technology, proud of it because it's generally the smart move for most of us. I test drive shiny things I can make time for, but bringing it into my stack doesn't happen by reading a few blogs. It not only requires significant technical merit, but someone has to maintain all this shit.

[_almosnow]

Could you provide an example? I'm using node and are pretty satisfied with the performance I have.

[hacknat]

K. From my personal experience it has held up quite well.

[SamReidHughes]

It's par for the course as far as event-loop I/O goes.