One thing that is not super clear from the blog post, and which may be a surpsise to some, is that Cloud Functions will require you to upload your source code. The compilation happens not on your end but on Google servers.<p>This is probably not a surprise for folks who have been using Python or Node for cloud functions, but it is something to think about.<p>Other FaaS providers don't have this requirement, and just take a Linux x86_64 binary.
Hey all - Seth from Google here. We're really excited to bring Go to Google Cloud Functions (GCF). Please try it out, give us feedback, and let us know if you have any questions!
As an aside, and since there are some googlers here, the heading animation on the blog has some issues in Firefox. They are super annoying. Would be nice if google supported all browsers.<p><a href="https://photos.app.goo.gl/MgsfH8GZndCdyBjeA" rel="nofollow">https://photos.app.goo.gl/MgsfH8GZndCdyBjeA</a>
We've used GCF for some production tasks and it's worked pretty well for us.<p>Would like to see some more runtimes/languages. I'm hoping AWS' recent layers implementation has made this more of a focus at Google. I'm curious how the implementation of Go has affected the ease of integrating other languages.
Isn't this all about to be replaced by serverless containers? With FaaS deployments just taking docker containers or building your code into one when you upload?<p>Why the continued work on a one-off runtime and http response spec instead?
Meta comment: why did the HN title change to "Go 1.11 is now a supported language"?<p>This post is specifically about Google Cloud Functions, not Go 1.11 in general (which is over 6 months old).<p>edit: thanks, mods!
> func F(w http.ResponseWriter, r *http.Request)<p>And me thinking the days of C compilers with 10 character limit for identifiers on the symbol table was long gone.