Why I went from Python to Go (and not node.js)

Re:Why I went from Python to Go (and not node.js) by erichocean on Friday September 14, 2012 @06:05PM (#4524234)

Until, that is, you tackle a problem for which one machine isn't big enough, at which time you need to do all of the "real" solutions anyway, and `go myfunction()` buys you...nothing.

There's way too much focus today on new languages that are designed to work on just one machine, and scale there – as if vertical scaling was the true problem we all face, when in fact, it's not. /sigh

[ Parent | on HN ]

Re:Why I went from Python to Go (and not node.js) by jeremyjh on Friday September 14, 2012 @09:49PM (#4524918)

He's talking about a web application doing a task asynchronously. There is no reason why it would be hard to scale Go web servers across multiple machines. Yes you could use a distributed broker system to do asynchronous tasks, and some languages platforms leave you no other choice, but there is no reason to think his use case actually requires anything more than running an asynchronous task.

[ Parent | on HN ]

Re:Why I went from Python to Go (and not node.js) by xyproto on Friday September 14, 2012 @06:36PM (#4524343)

Go is well suited for this too. Look at dozer at github.

[ Parent | on HN ]