News for hackers. Stuff that matters.
Re:The switch: Python to Node.js by viraptor on Sunday December 18, 2011 @06:46AM (#3366448)
I'd really like to see that spreadsheet, since there are many python frameworks other than twisted available. There are eventlets/greenlets, there's gevent, there's diesel and monocle for minimal things, etc. Makes you wonder what actually made them change the whole technology... Than again, they could probably even reuse pyjamas to still write node.js code in python...

OT: "We should of used SQLAlchemy. We should of built ..." I thought this expression was Bristol-specific. Apparently it's taking US too.

Re:The switch: Python to Node.js by LeafStorm on Sunday December 18, 2011 @07:42AM (#3366527)
In the Southern US, at least, "should have" commonly gets shortened into "should've," which sounds sorta like "should of." That's still no excuse for writing it.
Re:The switch: Python to Node.js by tikhonj on Sunday December 18, 2011 @07:40AM (#3366525)
I don't know if you missed the link or if it was added later, but it's here: https://docs.google.com/spreadsheet/ccc?key=0AvBGESHWxhk2dHJ...

It seems they looked at Gevent, Go, C++ and the JVM. As usual, no love for Haskell :(, not that they're entirely to blame there.

Re:The switch: Python to Node.js by reinhardt on Sunday December 18, 2011 @07:58AM (#3366551)
Too bad that the comparison doesn't make much sense: Node/Twisted/Gevent (language specific frameworks) vs Go/C++ (languages) vs JVM (platform).
Re:The switch: Python to Node.js by dextorious on Sunday December 18, 2011 @08:41AM (#3366596)
It's not like (language specific framework + language) is that different from (language + built-in features + standard library).
Re:The switch: Python to Node.js by viraptor on Sunday December 18, 2011 @09:25AM (#3366665)
Thanks, either I'm going crazy, or this wasn't a link before...
Re:The switch: Python to Node.js by lucian1900 on Sunday December 18, 2011 @12:48PM (#3367047)
It's very obviously skewed to get Node.JS as a winner.