Re:Introducing Swift Service Lifecycle
by pjmlp on Friday July 17, 2020 @03:22AM
(#23868047)
Google had no vision with Go, it was just a group of well known developers in the UNIX world that got fed up waiting for their C++ compile times, with a supporting manager that decided to fund their work.
Google is pretty much Java and C++ alongside their infrastructure, and OSes.
K8s prototype was started in Java and migrated to Go after some Go aficionados joined the team.
Besides k8s, you have Google download service (because someone from Go team bothered to port the service to Go), gVisor, parts of Android GAPI, the new internal Android build system, gVisor, and Fuchsia TCP/IP stack that apparently should be rewritten in C++/Rust.
And that is about it, as much as it comes outside.
Google is pretty much Java and C++ alongside their infrastructure, and OSes.
K8s prototype was started in Java and migrated to Go after some Go aficionados joined the team.
Besides k8s, you have Google download service (because someone from Go team bothered to port the service to Go), gVisor, parts of Android GAPI, the new internal Android build system, gVisor, and Fuchsia TCP/IP stack that apparently should be rewritten in C++/Rust.
And that is about it, as much as it comes outside.