Google submits Go apps container project to Cloud Native Computing Foundation
(2022/10/19)
- Reference: 1666206011
- News link: https://www.theregister.co.uk/2022/10/19/google_go_container_cncf/
- Source link:
Google has offered its tool for pure Go Kubernetes containers to the Cloud Native Computing Foundation (CNCF) ... and may have thought it was a done deal.
The CNCF is the Linux Foundation project that acts as the guardian of Kubernetes [1]since Google stepped away .
The [2]KO project is a tool for building application containers that contain pure Go apps – in the project's description:
A single Go application without any/many dependencies on the OS base image (e.g., no cgo, no OS package dependencies).
A now-deleted post on Google's open source blog yesterday [3]announced : "Google donates KO tool for simple fast and secure container image building to CNCF." However, this post was taken down and [4]republished with a new, slightly more measured title: "KO applies to become a CNCF sandbox project".
A [5]discussion on GitHub suggests that this might just be down to a misunderstanding over the submissions process to the CNCF [6]sandbox . This could be the case, but Google has managed such things before, for instance with Knative, "which builds on Istio to provide eventing and scaling services," as [7]we put it in 2020 . Google [8]denied it would hand this over in 2019, then [9]handed it to the CNCF in 2021.
[10]
We are probably going much too far, but we can't help but wonder if wanting to hand over the tooling might suggest waning enthusiasm for Go within Google.
[11]Zinc: An Ubuntu remix that dares to be different
[12]Oracle VirtualBox 7.0 is here – just watch out for the proprietary Extension Pack
[13]Red Hat backs CNCF project, spills TEE support over Kubernetes
[14]Hardening in the enterprise: SUSE releases Rancher 2.6.5 and NeuVector 5.0
Google's Go programming language is still developing: [15]version 1.19 came out a couple of months ago, and version 1.20 is in development. Even so, and despite [16]interest , Go 2 seems no closer than it was in 2018 when senior Go engineer Ian Lance Taylor [17]shared some ideas about it.
The [18]verdict of the Fuchsia team on Go in 2020 was also negative. Although it scored five "pros" against four "cons", the result was:
Decision: Go is not approved
Whereas in the last year or so, Rust is getting more attention and community support. Notably, [19]Google's new KataOS is "written almost entirely in Rust."
There's also been some notable informed criticism of Go in tech circles recently, including [20]"Lies we tell ourselves to keep using Golang" from "Faster Than Lime", a follow-up to the author's earlier [21]"I want off Mr Golang's Wild Ride" . We do note, though, that a key objection in the earlier article, that Go lacks generics, was remedied in Go [22]1.18 , released last March. ®
Get our [23]Tech Resources
[1] https://www.theregister.com/2018/08/30/google_kubernetes_project/
[2] https://github.com/ko-build/ko
[3] https://opensource.googleblog.com/2022/10/google-donates-ko-tool-for-simple-fast-and-secure-container-image-building-to-cn.html
[4] https://opensource.googleblog.com/2022/10/ko-applies-to-become-a-cncf-sandbox-project.html
[5] https://github.com/cncf/toc/pull/945
[6] https://www.cncf.io/sandbox-projects/
[7] https://www.theregister.com/2020/04/23/google_cloud_ceo_says_istio/
[8] https://www.theregister.com/2019/10/02/google_knative_will_not_be_donated_to_any_foundation/
[9] https://www.theregister.com/2021/12/01/knative_cncf/
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Y1BzdH8NhewiWC81rTo4EQAAANU&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[11] https://www.theregister.com/2022/10/13/zinc_ubuntu_remix/
[12] https://www.theregister.com/2022/10/11/oracle_virtualbox_7/
[13] https://www.theregister.com/2022/10/10/confidential_containers_encrypted_k8s/
[14] https://www.theregister.com/2022/05/17/suse_rancher_neuvector/
[15] https://go.dev/blog/go1.19
[16] https://www.sethvargo.com/what-id-like-to-see-in-go-2/
[17] https://github.com/golang/proposal/blob/master/design/28221-go2-transitions.md
[18] https://fuchsia.googlesource.com/fuchsia/+/refs/heads/master/docs/contribute/governance/policy/programming_languages.md#Go
[19] https://www.theregister.com/2022/10/17/google_kata_os/
[20] https://fasterthanli.me/articles/lies-we-tell-ourselves-to-keep-using-golang
[21] https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride
[22] https://tip.golang.org/doc/go1.18
[23] https://whitepapers.theregister.com/
The CNCF is the Linux Foundation project that acts as the guardian of Kubernetes [1]since Google stepped away .
The [2]KO project is a tool for building application containers that contain pure Go apps – in the project's description:
A single Go application without any/many dependencies on the OS base image (e.g., no cgo, no OS package dependencies).
A now-deleted post on Google's open source blog yesterday [3]announced : "Google donates KO tool for simple fast and secure container image building to CNCF." However, this post was taken down and [4]republished with a new, slightly more measured title: "KO applies to become a CNCF sandbox project".
A [5]discussion on GitHub suggests that this might just be down to a misunderstanding over the submissions process to the CNCF [6]sandbox . This could be the case, but Google has managed such things before, for instance with Knative, "which builds on Istio to provide eventing and scaling services," as [7]we put it in 2020 . Google [8]denied it would hand this over in 2019, then [9]handed it to the CNCF in 2021.
[10]
We are probably going much too far, but we can't help but wonder if wanting to hand over the tooling might suggest waning enthusiasm for Go within Google.
[11]Zinc: An Ubuntu remix that dares to be different
[12]Oracle VirtualBox 7.0 is here – just watch out for the proprietary Extension Pack
[13]Red Hat backs CNCF project, spills TEE support over Kubernetes
[14]Hardening in the enterprise: SUSE releases Rancher 2.6.5 and NeuVector 5.0
Google's Go programming language is still developing: [15]version 1.19 came out a couple of months ago, and version 1.20 is in development. Even so, and despite [16]interest , Go 2 seems no closer than it was in 2018 when senior Go engineer Ian Lance Taylor [17]shared some ideas about it.
The [18]verdict of the Fuchsia team on Go in 2020 was also negative. Although it scored five "pros" against four "cons", the result was:
Decision: Go is not approved
Whereas in the last year or so, Rust is getting more attention and community support. Notably, [19]Google's new KataOS is "written almost entirely in Rust."
There's also been some notable informed criticism of Go in tech circles recently, including [20]"Lies we tell ourselves to keep using Golang" from "Faster Than Lime", a follow-up to the author's earlier [21]"I want off Mr Golang's Wild Ride" . We do note, though, that a key objection in the earlier article, that Go lacks generics, was remedied in Go [22]1.18 , released last March. ®
Get our [23]Tech Resources
[1] https://www.theregister.com/2018/08/30/google_kubernetes_project/
[2] https://github.com/ko-build/ko
[3] https://opensource.googleblog.com/2022/10/google-donates-ko-tool-for-simple-fast-and-secure-container-image-building-to-cn.html
[4] https://opensource.googleblog.com/2022/10/ko-applies-to-become-a-cncf-sandbox-project.html
[5] https://github.com/cncf/toc/pull/945
[6] https://www.cncf.io/sandbox-projects/
[7] https://www.theregister.com/2020/04/23/google_cloud_ceo_says_istio/
[8] https://www.theregister.com/2019/10/02/google_knative_will_not_be_donated_to_any_foundation/
[9] https://www.theregister.com/2021/12/01/knative_cncf/
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Y1BzdH8NhewiWC81rTo4EQAAANU&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[11] https://www.theregister.com/2022/10/13/zinc_ubuntu_remix/
[12] https://www.theregister.com/2022/10/11/oracle_virtualbox_7/
[13] https://www.theregister.com/2022/10/10/confidential_containers_encrypted_k8s/
[14] https://www.theregister.com/2022/05/17/suse_rancher_neuvector/
[15] https://go.dev/blog/go1.19
[16] https://www.sethvargo.com/what-id-like-to-see-in-go-2/
[17] https://github.com/golang/proposal/blob/master/design/28221-go2-transitions.md
[18] https://fuchsia.googlesource.com/fuchsia/+/refs/heads/master/docs/contribute/governance/policy/programming_languages.md#Go
[19] https://www.theregister.com/2022/10/17/google_kata_os/
[20] https://fasterthanli.me/articles/lies-we-tell-ourselves-to-keep-using-golang
[21] https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride
[22] https://tip.golang.org/doc/go1.18
[23] https://whitepapers.theregister.com/
Go won't survive
Ever since the debacle that was AngularJS (specifically, they way they tossed v1 in the garbage and came out with v2 that was completely different), I have been distrustful of any language that Google might come out with. Google treats its languages with the same distaste as it treats all its other products. ie: badly. I don't have the time to learn an entirely new language every couple weeks cause the previous widget isn't cool anymore.
Their entire collective workforce has a worse attention span than a single squirrel hopped up on amphetamines.