> Fire and Motion. You move towards the enemy while firing your weapon. The firing forces him to keep his head down so he can’t fire at you. ... The companies who stumble are the ones who spend too much time reading tea leaves to figure out the future direction of Google. People get worried about kubernetes and decide to rewrite their whole architecture for kubernetes because they think they have to. Google is shooting at you, and it’s just cover fire so that they can move forward and you can’t
Felt the same about Polymer. Starry eyed devs open a pre-webpack build terminal, import the if (no else!) and for keywords, build dom nodes manually and tolerate a terrible debugging experience. Youtube loads a few seconds slower in Firefox, since it gets served a polyfil of a runtime and a slower build; Chrome had a head start with a native runtime. Sites built by starry eyed developers simply break on Firefox.
Perhaps @thockin can comment since this was on his Twitter some time ago, but I believe Google is starting to use it more and more internally. He would know, since he's been involved since the beginning.
Anecdotal, but I know a guy working as a senior Engineer at Google with some central server-side components for the Android ecosystem. He had barely heard the word Kubernetes when we last spoke, let alone knew what it was.
For the record, the Google developers I know also don't use it and generally don't care about it. But it's a big company, I'm sure they have a few users
I didn't say it was the same codebase. "Inspired" may be more accurate but the point still remains that the concepts in Kubernetes have a direct path to the concepts in Borg.
