News for hackers. Stuff that matters.
Re:Cloud Functions: Go 1.11 is now a supported language by sjeanpierre on Wednesday January 16, 2019 @02:42PM (#18924275)
Is there a reason dependency management happens like this? We currently deploy Go Lambda functions in AWS with the help of the Serverless Framework and it just uploads the cross compiled Binary and not the whole project.

Why wouldn't the binary be the deployed unit in this case?

Re:Cloud Functions: Go 1.11 is now a supported language by ehsankia on Thursday January 17, 2019 @03:03AM (#18929161)
While it's a lot more work for them, and some may already have the infrastructure setup for deploying their own binary, I think having GCP handle the end-to-end there is more user friendly in general. I can quickly write a Cloud Function from any computer, without having to deal with setting up the tool chains. If you want to just run binaries, sounds like Cloud Functions isn't what you're looking for.
Re:Cloud Functions: Go 1.11 is now a supported language by pstuart on Wednesday January 16, 2019 @03:27PM (#18924768)
Maybe Google Native Client support?

https://github.com/golang/go/wiki/NativeClient

Re:Cloud Functions: Go 1.11 is now a supported language by chrisbroadfoot on Wednesday January 16, 2019 @03:31PM (#18924815)
No, it's not related to this. GOOS=linux and GOARCH=amd64 for GCF deployments. The sandboxing technology used is based on gVisor.

We're working on arbitrary binary deployments, you can sign up for that here: g.co/serverlesscontainers

Disclaimer: I work on GCP.