cwonrails
12/7/2015 - 4:18 PM
The Case For Go #golang
The Case For Go #golang
The Case For Go
- Iron.io: How We Went from 30 Servers to 2 with Go
- Go at Google: Language Design in the Service of Software Engineering
- Behind the Scenes: Big Data at Torbit
- pool.ntp.org DNS server in Go
- Juju at Canonical
- Go at bitly
- NSQ: realtime distributed message processing at scale
- CloudFlare blows hole in laws of Web physics with Go and Railgun
- Go as an alternative to Node.js for Very Fast Servers
- Why I Like Go
- Why I Program in Go
- dl.google.com now served by Go
- Google's Go Programming Language Grows Up: Now What?
- Moving to Go
- Rob Pike: Why Learn Go?
- Go At Conformal
- Why I went from Python to Go (and not node.js)
- Another go at the Next Big Language
- @tobi: "I have now completed two projects in Go. I predict that it's going to be the dominant language for server work."
- @derekcollison: "Prediction: Go will become the dominant language for systems work in IaaS, Orchestration, and PaaS in 24 months."
- Will Go be the new go-to programming language?
- PARALLELISM FOR THE WIN!
- Go is boring
- Dr. Dobb's: Why Not Go?
- Google I/O 2012: Go in production
- Go at Novartis
- Go at the BBC
- Go at SoundCloud
- Go at Moovweb
- Building StatHat with Go
- Go at CloudFlare
- Why you PHP guys should learn Golang
- I/O BootCamp 2011: Real World Go
- Go at Heroku