News for hackers. Stuff that matters.
Re:Node.js is Cancer (2011) by JonnieCache on Thursday November 14, 2013 @12:31PM (#6733704)
I dunno...

"I know there's a closed form solution. Shouldn't you be in front of a mirror somewhere, figuring out how to introduce yourself to her?"

is pretty great.

Re:Node.js is Cancer (2011) by LaGrange on Thursday November 14, 2013 @12:41PM (#6733791)
If you’re a teenager then yes. Otherwise, it’s an ad persona towards an expected legitimate complaint: „hey, maybe a lot of work actually isn’t CPU-bound?” Seriously, if you can’t discern between solution for CPU-bound and IO-bound problems, you should consider a different career.
Re:Node.js is Cancer (2011) by GhotiFish on Thursday November 14, 2013 @12:51PM (#6733897)
I think the author didn't spell out the issue with that useless bit of trivia because the issue is obvious. Whether the implementation of the function is inefficient or not is immaterial to the argument. Most things arn't CPU bound, some things are. So the complaint stands.
Re:Node.js is Cancer (2011) by JonnieCache on Thursday November 14, 2013 @12:48PM (#6733872)
Calling me a teenager, and then accusing the article of ad hominem six words later. Superb.