FroshKiller All American 51911 Posts user info edit post |
The first GopherCon concluded this weekend, and Go 1.3 beta has been released. Go is in production use at scale at YouTube, Heroku, SoundCloud, etc. It seems pretty mature. Anyone implemented a for-realsies project in Go? Also, I'm going to type "golang" in this post just for searchability. 4/28/2014 8:30:11 AM |
d357r0y3r Jimmies: Unrustled 8198 Posts user info edit post |
Using it now to write a fairly simple REST API for a side project. The language is simple enough; I've mostly rolled my own solutions except for encryption and routing. It really only took about a week to get up to speed. If you're jumping into C++, Java, C#, you've got decades of API to learn. With Go, you should be able to get 90% of the way quickly, assuming you've already got a few languages under your belt.
Lack of generics has annoyed me a couple of times, but I've always been able to find other ways to do mostly the same thing with interfaces.
I'm using Google App Engine to deploy at the moment. I've never really messed with PaaS much, but it's a great option for someone that is trying to independently release some sort of MVP. I really don't want to spend hours trying to hack together a server; I'm not a system admin.
The lack of tooling is expected but frustrating at times. I'm used to writing C# and Typescript in Visual Studio, alongside sweet, sweet Resharper. With Go, just getting autocomplete took some work, and that's about as good as it gets right now.
[Edited on November 2, 2014 at 11:40 PM. Reason : ] 11/2/2014 11:39:24 PM |