I've been trying out App Engine for Go the last couple weeks for a side project, but it's been a bit of a headache. Having to use their data store was a little annoying to begin with, but I was able to get past that one. Once I started playing with user accounts I was very frustrated to learn that they only support Google Account login functionality... I have been looking at implementing my own but Go doesn't appear to have a common authentication package and the advice often seems to be "roll your own". Any advice for doing this?<p>That said, this is the only Go hosting service I could find that has a free tier and their development binaries are very well done!
I've been using Go on App Engine for the past 6 months for a weekend project. My goal is to build a little search engine for Swift language/iOS resources. At the moment, I don't crawl any sites, just search titles and tags. I've been happy with the performance. Seems snappy?<p><a href="http://www.h4labs.com/dev/ios/swift.html" rel="nofollow">http://www.h4labs.com/dev/ios/swift.html</a><p>Anyway, I'd like to hear from other Go web developers. Libraries, frameworks, etc that work well on App Engine.
Whether to use Go on App Engine or not is a much less important question than whether to use App Engine or not. Java is also a good choice on App Engine. But either way, using App Engine dramatically affects almost any decision you'll make about how to build, and it ties your fortune to the sometimes-capricious product decisions made for App Engine.
I have been really enjoying Go App Engine support for some time now. It's pretty convenient to write web apps in Go, although to be fair all my projects have been super simple. I don't really have any experience making anything beyond a simple forum.
Nice! I've been using this for a few years for my Scrabble solver app but it's good to know they've committed to it for the long term :).
PSA: Google is notorious for blatantly lying about App Engine availability. Today’s yellow alerts and red exes, on the uptime/status page, somehow always become yesterday's green checks.<p>(This was a first-hand source of frustration for the team I was working with a few years ago.)<p>You have been warned.