Node.js Is Bad Ass Rock Star Tech

If you haven't seen it, you might find this entertaining: [VIDEO] I really wish gar1t would make some new videos, I love them.

> What specifically is the problem with asyncio? Watch the very NSFW (lots of swearing) but hysterically funny video "node.js is bad ass rock star tech" on youtube sometime ;). [VIDEO]

>We know the java libraries are there for lots of things, but Node is all about async and handling thousands of connections. It does this by forcing the entire ecosystem to be async too (including things like database drivers). By using a Java JDBC database driver you're completely losing any async support. Same presumably goes for redis or Mongo drivers. You can do some of the work with threads and pooling, but it's still not the same, and makes this another useless micro benchmark. Sounds like you're quoting from the "Node.js Is Bad Ass Rock Star Tech" satire video ( [VIDEO] ). Nothing inherently special about "forcing the entire ecosystem to be async too", especially since Node is more or less FORCED to do that, because javascript is single threaded. Add the bad callback spaghetti implementation of async, and the main benefit of Node is easy deployment, and accessibility to the millions of javascript programmers. As an async environment it doesn't offer anything either new or too compelling.

Folks, why are you upvoting this? It only talks about CPU usage, Node not being Unixy enough, and Javascript being terrible. A better critique would have included talks about callback hell, or the general philosophical issues of non-block/evented work versus synchronous programming: see the classic [VIDEO] . This isn't even that great a rant. (I appreciate my fellow Rails devs probably upvoting it out of spite, but c'mon...)

I disagree with the premise. I cannot imagine a better latency experience than blocking loop IDEs like VS6. Which inputs are getting latency? The keyboard? The files? > the non blocking nature [VIDEO]

Why would a company that uses Java even consider Node.js? Java is hands down faster. I have never seen a benchmark that showed Node coming even close to Java performance. [VIDEO]

Perhaps this can help: [VIDEO] (Unless you were being double-sarcastic, in which case this post is a fail)

"I don't know much about Spring, but In Vert.x 1.x each Verticle that is deployed has its own classloader, so it's hard to share a context across verticles." -- Tim Fox (Vertx creator) "A vert.x instance guarantees that a particular verticle instance is always executed by the exact same thread. This gives you a huge advantage as a developer, since you can program all your code as single threaded. Well, that won't be a big deal to you if you are coming from JavaScript where everything is single threaded, but if you're used to multi-threaded programming in Java, Scala, or even Ruby, this may come as a huge relief" -- lol [VIDEO]