3 ms·
That was supposedly 17 years ago, so I was counting it in the good old. It was cutting-edge at the time, then years later PyTorch ate its lunch, which they even
by frollogaston 3mo ago
That was supposedly 17 years ago, so I was counting it in the good old. It was cutting-edge at the time, then years later PyTorch ate its lunch, which they eventually admitted with TF 2.0.
- vintermann 3mo agoJokes aside, I think a lot of the famous Google internals that became public (Tensorflow, Kubernetes, Bazel, Angular), although I heard everyone say they worked so much better inside Google than outside it, had issues. And the Facebook-supported rivals were often just so much more pleasant to work with that you couldn't ignore it. For all else that was bad about Facebook, for a few years they were pretty good at denying Google technical hegemony.
- antoinealb 3mo agoTangent nit, but k8s was never a google-internal system. See https://research.google/pubs/borg-omega-and-kubernetes/ https://research.google/pubs/borg-omega-and-kubernetes/
- frollogaston 3mo agoDefinitely a thing with Angular and TF. Blaze works well within Google's monorepo for sure, but idk what it's like using Bazel outside. Never used Kubernetes in Google.