Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Felix, given that the rest of your stack is on Node, what made you choose Go?


Node.js was a good choice for Transloadit when we started (2009). By good I mean better than PHP which we tried using for transloadit before.

I started playing with Go late last year, so far I'm under the impression that it's easier to write reliable software with it than node.js. Callbacks and exception handling are a huge PITA in node.js, and the community has chosen to refuse improvements that would help with some of the issues (promises).

Go is also an incredible joy to work with given the modern nature of the standard library, static typing, gofmt, built-in testing, and many other small things that the Go team has done right.

That being said, tus.io is not a Go project. Our first server implementation (tusd) is written in Go, but we're working on support for other plattforms like node.js as well.

Generally speaking node.js will continue to be part of our toolkit at Transloadit (for the quick & dirty), but I suspect that we'll use Go for the more criticial parts we work on going forward.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: