Node.js has jumped the shark

#1

Post by bascule » Tue, Oct 04, 2011, 4:10 PM UTC

Node.js has jumped the shark
unlimitednovelty.com

Re: Node.js has jumped the shark

#2

Post by klochner » Tue, Oct 04, 2011, 4:38 PM UTC

Best part of the post was where someone suggested he increase his heap size to 1GB to get a fibonacci algorithm to run.

   After pointing this out, a member of the Node.js
   community (post now deleted) suggested I might have an
   obsolete version of Node with a 1GB heap limit and that
   I recompile without the 1GB restriction so that this 
   retarded algorithm can continue eating up all my system RAM.

Re: Node.js has jumped the shark

#3

Post by jevinskie » Tue, Oct 04, 2011, 4:40 PM UTC

Isn't it the point of all this madness that jumping the shark for these small and trivial problems is fun and thought provoking?

Re: Node.js has jumped the shark

#4

Post by Miky » Tue, Oct 04, 2011, 4:45 PM UTC

jevinskie wrote: post #3

Isn't it the point of all this madness that jumping the shark for these small and trivial problems is fun and thought provoking?

Jumping the shark is the moment when something, such as a TV show, or in this case a community around a web framework, begins to decline in quality beyond recovery, so “jumping the shark for these small and trivial problems” really doesn't make sense.

Re: Node.js has jumped the shark

#5

Post by thenduks » Tue, Oct 04, 2011, 4:46 PM UTC

Hmm, sounds more like reddit is the thing that has jumped the shark :)

Most people using Node I've had contact with are firmly in the 'right tool for the job' camp. No one sane does CPU intensive tasks inside the event loop... that's what delayed job processor stuff is for.

Re: Node.js has jumped the shark

#6

Post by [deleted] » Tue, Oct 04, 2011, 4:48 PM UTC

[deleted]

Re: Node.js has jumped the shark

#7

Post by ntoshev » Tue, Oct 04, 2011, 4:49 PM UTC

This only proves that many in node.js community and some trolls outside of it don't really understand programming at the event level, BUT insist on writing about it.

First, you shouldn't judge anything by the worst of its kind.

Second, why I keep seeing related stories piling one misunderstanding on top of another on Hacker News?

Re: Node.js has jumped the shark

#8

Post by jeffreymcmanus » Tue, Oct 04, 2011, 4:50 PM UTC

I remember having debates like this about the TRS-80 in middle school. These guys need to give it a rest, srsly.

Re: Node.js has jumped the shark

#9

Post by [deleted] » Tue, Oct 04, 2011, 4:52 PM UTC

thenduks wrote: post #5

Hmm, sounds more like reddit is the thing that has jumped the shark :) Most people using Node I've had contact with are firmly in the 'right tool for the job' camp. No one sane does CPU intensive tasks inside the event loop... that's what delayed job processor stuff is for.

[deleted]

Re: Node.js has jumped the shark

#10

Post by wavephorm » Tue, Oct 04, 2011, 4:53 PM UTC

I don't see how discussions like this signify the decline of NodeJS. Quite the opposite. Lots of people are thinking about how to do this kind of computation the right way, within the context of NodeJS.

Honestly this discussion has kind of highlighted how bad almost all other platforms are and how much room for improvement there is.