borg

Kubernetes is not a clone of Borg - it is inspired by the lessons and experiences we got by doing Borg.

But keep in mind that we don't want or need everything that Borg has, and Borg does not have everything that Kubernetes does.

However, visible XML configurations are a symptom that your app is about to be assimilated into the borg collective.

This is just another example, an open source version of Borg that will always be a few years behind.

Your friends will either be assimilated by the Borg or shot out of a torpedo tube.

While it is true that Borg is 10 years ahead of Kubernetes, we have the benefit of knowing where Borg arrived rather than following the same winding course.

Only people who think and express themselves within HN's borg-like ideological parameters can coexist here.

Take a look at google, they always try to bring costs down, through things like borg, kubernetes, etc.

To work at the borg you must learn and play by the borgs rules!

If we can get 75% as functional as Borg in 1/3 the time, we'll be doing pretty darn well.

It's a measure of how false your first paragraph is that I can't guess which way your imaginary Borg leans.

I used Borg for a while in 2013, and it was amazingly, specially the logging for tracking down runtime problems.

Of course, but unless there is a massive maintainability flaw in Borg, its unlikely you can duplicate 10 years of effort AND maintain pace with Borg's/Borg's successor(s) progress.

If you say or believe something not in harmony with The Borg, you'll soon be talking to yourself only.

When I was at Google building a microservices based system was so much easier with Borg, Dapper, etc.