The switch: Python to Node.js

Re:The switch: Python to Node.js by peregrine on Sunday December 18, 2011 @09:49AM (#3366690)

I'm curious as to why Go wasn't a final contender? It started off with Go being a crowd favorite and ended with it nowhere. I assume it has to do with the young package repository but what's the reasoning you used?

[ Parent | on HN ]

Re:The switch: Python to Node.js by pquerna on Sunday December 18, 2011 @11:41AM (#3366901)

Go's core packages are good.

Go's not-in-core packages are a mixed bag. Lots of "one off" experiment projects. Which is fine, thats where it is in its life. Node.js was in the same place packages wise 18 months ago.

Additionally, at the time we were looking at this, Go was still doing releases every 2 weeks -- this was months before the Go 1.0 plan was even announced: http://blog.golang.org/2011/10/preview-of-go-version-1.html

[ Parent | on HN ]

Re:The switch: Python to Node.js by peregrine on Wednesday December 21, 2011 @12:14PM (#3378212)

Thanks! I am playing around with Go and you are right the packages are a mixed bag. Not to mention using a search engine is basically impossible.

[ Parent | on HN ]