Btw, in a world where energy is supposedly scarce, how do people justify using languages (Python, Ruby, I'm looking at you) that are an order or two magnitudes slower than they need to?
Node.js cures cancer
21–30 of 99 posts
Re: Node.js cures cancer
#22As a cancer survivor, just wanted to let you know that the poor taste exhibited here is pretty sad. When you want to make your point next time, use a title that doesn't include something that kills people. Thank you.
[deleted]
Re: Node.js cures cancer
#23guys guys guys. you do realize ted is trolling us all right (go look at his twitter @dozba right now. I think he is having a great time). he is a pro at this ( http://teddziuba.com/2011/07/the-craigslist-reverse-programm... ) Also if his thoughts on node.js don't annoy you enough go take a look at his archive: http://teddziuba.com/archives.html . He blogs/trolls/thinks about NoSQL, OS X, twisted/tornado, python, queu…
Those new to NodeJS will still read this trolled post and find real gems of info here. So all is not lost.
Re: Node.js cures cancer
#24I'm getting 0.020s tops for that fibonacci code on node (time curl http://localhost/), even going up to `1.1210238130165696e+167` (800th number). OSX Lion on a C2d 2.3ghz.
Python 2.7.1 took 1m25.259s (no server).
Am I doing something wrong? Or is there some incredibly optimized code path for OSX?
edit: even weirder, `time node fibonacci.js` without a server takes 0.090s.
Re: Node.js cures cancer
#25As a cancer survivor, just wanted to let you know that the poor taste exhibited here is pretty sad. When you want to make your point next time, use a title that doesn't include something that kills people. Thank you.
Like, node is the bomb?
I am sure cancer sucks more than anything I had to experience but the world is not going to change its figures of speach for you and it is not directly derogatory at all it just reminds you of your misfortune.
Btw I am not criticizing you for asking the OP to change his headline I just think it is an impossible crusade.
Re: Node.js cures cancer
#26As a cancer survivor, just wanted to let you know that the poor taste exhibited here is pretty sad. When you want to make your point next time, use a title that doesn't include something that kills people. Thank you.
Like, node is the bomb? I am sure cancer sucks more than anything I had to experience but the world is not going to change its figures of speach for you and it is not directly derogatory at all it just reminds you of your misfortune. Btw I am not criticizing you for asking the OP to change his headline I just think it is an impossible crusade.
See how I just typed crusade and pressed send without thinking.
Re: Node.js cures cancer
#27Earlier quoted context omitted.
I would argue that heavily CPU-bound stuff shouldn't be run in a web app. It's much better to offload the task to a worker system via redis/zeromq/kestrel/etc. The majority of activity you see in every web app I've ever designed has been almost exclusively I/O bound.
That's cool and all but in the real world we gotta get it done.
Wait, I think I've missed something because that response seems overly dismissive. How is offloading CPU-intensive stuff to a worker system not getting it done?
Re: Node.js cures cancer
#28Earlier quoted context omitted.
One Node process is reduced to doing the trivial work, like you'd have in any other system. Nothing is preventing the other processes from also being Node.
True, and in fact, this is how nginx works: the process that owns the event loop is separate from the process(es) that does the work. This is a decent way of mixing an event loop and multi-core processing, but with Node, you're forced to marry the HTTP server to the application, which is a dangerously tight coupling of responsibilities. If you really want to do something silly like write your application in server-si…
I'm not sure if many people are choosing Node just because they're familiar with JavaScript. Most people would probably rather be less familiar with JavaScript. More likely they're choosing it because the runtime is very fast and a lot of libraries are packaged for it.
The WSGI/CGI bit is in fact mentioned in the article. :)
Re: Node.js cures cancer
#29guys guys guys. you do realize ted is trolling us all right (go look at his twitter @dozba right now. I think he is having a great time). he is a pro at this ( http://teddziuba.com/2011/07/the-craigslist-reverse-programm... ) Also if his thoughts on node.js don't annoy you enough go take a look at his archive: http://teddziuba.com/archives.html . He blogs/trolls/thinks about NoSQL, OS X, twisted/tornado, python, queu…
> he is a pro at this (http://teddziuba.com/2011/07/the-craigslist-reverse-programm...)
The Craigslist Reverse Programmer Troll is clever. While it's openly a troll, it makes a good point. Worth reading.
Re: Node.js cures cancer
#30dboza is pretty awesome, beck didnt really address the underlying issue. If you have any real computation, node.js is not your solution. I figured out this in event-driven IO back when I was in school 15 years ago fffffff