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

One of the places Go excels is at sharing memory between goroutines. Most web apps are built so that each request is independent of all other requests. Which isn't to say Go's a bad fit for all web apps, I just don't think most will gain anything from it.

We've used it for just another web app, and haven't gotten any value of out it...except learning Go. Then we deployed it as a piece of infrastructure, something that would have been hard to write in Node or Ruby, and it's been a real win.



Here's a big one: you can write your routines in a completely synchronous, blocking style. The Go runtime automatically async-izes that for you.

This is like getting the benefit of an evented system without paying the cost of structuring your code with callbacks (or other workaround).




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

Search: