I'm not trying to stir shit up...buuut it seems odd that an announcement for a Google Cloud product is being published on the Go project's blog?
I say this as a huge fan of Google Cloud and the experience of using Go on App Engine.
App Engine’s New Go 1.11 Runtime
41–50 of 101 posts
Re: App Engine’s New Go 1.11 Runtime
#42I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…
How long will the legacy App Engine APIs continue to work? Will they be removed before the runtime is GA?
These new runtimes seem amazing (and fix a lot of problems), but we also lose a ton of functionality that made app engine so desirable (easy users auth, images api, built in email sending, search, cron, and others).
It kind of feels like we've thrown the baby out with the bathwater.
Re: App Engine’s New Go 1.11 Runtime
#43I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…
Hey buss, thanks for stopping by.
How do you feel about the distinction between Google and Go? It sometimes feels like they're joined at the hip, something which historically had made people queasy (Java and Oracle, .NET and Microsoft, etc). Though Go is a project which came from Google, I personally feel that it better serves the interests of the Go community to treat them separately. Google receives special treatment from Go - the announcement that AWS Lambda would support Go did not receive similar fanfare on golang.org.
Side note: there is some activity on the Go blog which is more mutual cooperation and less Google hivemind:
https://blog.golang.org/go-cloud
But I still wonder why this stuff belongs here.
Re: App Engine’s New Go 1.11 Runtime
#44I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…
Any plans to support the cloud endpoints with the standard env? Wondering if the new runtime would be able to be embed that. That would be only reason for me not to switch from flex env.
(GAE PM)
Cloud Endpoints currently runs on GAE Standard Gen 1 and GAE Flex. We're investigating a solution for GAE Standard Gen 2 (which go 1.11 is, along with python 3.7, node 8, etc.) and GCF.
Re: App Engine’s New Go 1.11 Runtime
#45Earlier quoted context omitted.
Not worried about secrets in repo?
Tech Lead of Google Registry ( https://registry.google ) here. We run on GCP. You definitely don't want to check secrets into the repo for the same reason you don't set them as environment variables: It's not secure. The solution is to use Cloud Key Management Service. More info here: https://cloud.google.com/kms/ We use that to either store secrets directly, or to decrypt encrypted entities in a DB (e.g. Datastore).…
Another great resource: https://sethvargo.com/secrets-in-serverless/
Shows how to encrypt env vars with Cloud KMS then decrypt them in memory.
Re: App Engine’s New Go 1.11 Runtime
#46Earlier quoted context omitted.
Not worried about secrets in repo?
Tech Lead of Google Registry ( https://registry.google ) here. We run on GCP. You definitely don't want to check secrets into the repo for the same reason you don't set them as environment variables: It's not secure. The solution is to use Cloud Key Management Service. More info here: https://cloud.google.com/kms/ We use that to either store secrets directly, or to decrypt encrypted entities in a DB (e.g. Datastore).…
It’d be awesome if app engine had an easy way to add this like Firebase does.
P.s typo on your link
Re: App Engine’s New Go 1.11 Runtime
#47Hmm, I was just running into some context annoyances but this seems to remedy some nuances regarding that. Cool! Good timing! I’m assuming urlfetcher is deprecated now too? I’ll go read the migration guide now ... Awesome work! Love Go and GAE! Very happy so far.
You can use net/http to fetch URLs now :) Glad you're enjoying both Go and GAE!
What was the reason urlfetcher had to be engineered in the past? Curious.
Re: App Engine’s New Go 1.11 Runtime
#48Earlier quoted context omitted.
It is quite lightweight, yes! Though...I wouldn't necessarily call Python slow! Python keeps getting faster, and we now support Python 3.7 on our second gen runtimes: https://cloud.google.com/blog/products/gcp/introducing-app-e...
Does anyone have numbers to compare? Go is a compiled language. Should perform much better. Python might be perfectly acceptable of course.
I would absolutely love those numbers too. Always wondered about the working set of a minimal program, and also one with database access.
Re: App Engine’s New Go 1.11 Runtime
#49Earlier quoted context omitted.
You can use net/http to fetch URLs now :) Glad you're enjoying both Go and GAE!
What was the reason urlfetcher had to be engineered in the past? Curious.
I don't think I can say much more than: technical choices that required a different path to fetch resources from the broader internet.
Re: App Engine’s New Go 1.11 Runtime
#50Earlier quoted context omitted.
Not worried about secrets in repo?
Tech Lead of Google Registry ( https://registry.google ) here. We run on GCP. You definitely don't want to check secrets into the repo for the same reason you don't set them as environment variables: It's not secure. The solution is to use Cloud Key Management Service. More info here: https://cloud.google.com/kms/ We use that to either store secrets directly, or to decrypt encrypted entities in a DB (e.g. Datastore).…
Also, the NYTimes just published their project which integrates with HashiCorp's Vault: https://open.nytimes.com/open-source-simplifying-serverless-...