Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The "cloud" has been overhyped up the wazoo for years. That doesn't make PaaS meaningless or less useful.

PS. Could you point out a few egregious examples of the node community overhyping Node.js?



Well, to quote Ryan Dahl: "i wish for less #nodejs hype."

https://twitter.com/#!/ryah/status/8519974729

Also, I regularly see people making claims like "You can’t shoot yourself in the foot in any way" (http://venturebeat.com/2012/01/24/node-at-google-mozilla-yah...) and other variations involving issues around performance and concurrency.

I think it stems from some very smart people talking about why Node is better, then others trying to articulate the same thing without completely understanding what they're saying.


"You can’t shoot yourself in the foot in any way" is a pretty silly thing to say, but that seems to be an off-hand, casually made comment. None of this seems particularly egregious.

I'm looking for examples such as people actively promulgating Node adoption with ridiculous claims, people advising folks to use Node for specific tasks where it's completely unsuitable, people selling Node based technologies that aren't that good, people making the claim that Node is a silver bullet very publicly to a large audience, etc.



I'm not impressed by this example. You could use the same words to describe nginx to some degree. "Do something that hasn't been done before" isn't a crazy amount of hype, in my opinion.


Event loops and asynchronous reactor patterns have been around since what, the late 70s? Node "callback soup" is isomorphic to the structured programming models of dataflows and transactional architectures. Event-reactor systems with asynchronous libraries have been present in almost every language I've ever encountered--hell, even Modula-2, a fucking ancient Pascal derivative, had coroutines which supported exactly this kind of interleaved or reacted control flow.

You could have used any other language, for literally decades prior to Node's existence, to build the same things. Even if you didn't want to build a totally evented system, judicious use of select/epoll allows you to reap the benefits of asynchronous I/O without locking your whole application into the event loop.

Node.js programmers are building concurrent applications on a platform without coroutines, without fork/join, without threads, indeed without any parallelism, without scheduler priorities, hell without integers--and claiming it's a new paradigm in computing.

I consider that a joke.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: