News for hackers. Stuff that matters.
Re:How Kubernetes Broke Git by t3rabytes on Sunday July 31, 2022 @07:19AM (#32294815)
I feel the title is incorrect. This isn’t so much a critique of Git, it’s a critique of the way Kubernetes-the-project uses it.
Re:How Kubernetes Broke Git by TacticalCoder on Sunday July 31, 2022 @08:00AM (#32294969)
> This isn’t so much a critique of Git, it’s a critique of the way Kubernetes-the-project uses it.

I'd hope so: the Linux codebase is an order of magnitude bigger than the K8s one and it's not breaking Git.

Re:How Kubernetes Broke Git by _fat_santa on Sunday July 31, 2022 @09:39AM (#32295398)
He mentioned in the article that Kubernetes didn’t have a Linus Tovalds to oversee the project. I found a similar thing to be true with git, as often scaling isn’t so much a technical challenge at first, rather it’s a bunch of org challenges that manifest themselves in technical ways.

The model of the “benevolent dictator” kinda works in this case. My last project I was on we managed to scale to about 50k LOC without anything special, the key is I knew the repo like the back of my hand and could catch potential integration issues. While the model works well, it’s very hard to setup as you need a real nerd of a team lead to constantly watch the repo.

Re:How Kubernetes Broke Git by thrashh on Sunday July 31, 2022 @02:06PM (#32297338)
I don’t see why a project should strive for a lack of leadership

Most things in life that don’t have leadership become messy and disorganized and eventually disintegrate into an unstable hell with no real focus

Re:How Kubernetes Broke Git by tedmiston on Sunday July 31, 2022 @03:40PM (#32298144)
"How Kubernetes' usage of git (and GitHub) did not scale well post-monorepo"
Re:How Kubernetes Broke Git by tedmiston on Sunday July 31, 2022 @03:42PM (#32298158)
"How my nail broke hammers"
Re:How Kubernetes Broke Git by speed_spread on Sunday July 31, 2022 @08:50AM (#32295174)
The title is correct as it blames k8s for mishandling git and "breaking" it. It's not git's fault.
Re:How Kubernetes Broke Git by Karellen on Sunday July 31, 2022 @09:47AM (#32295440)
I'm still not quite sure how that counts as breaking git?

If you misuse a tool, and the tool performs poorly at the job it's not designed for, but never fails in an unexpected way, and still maintains all the functionality it always had, how have you broken that tool?

If try to hammer in a nail with the butt of a screwdriver, and make a complete pigs ear of it, but the screwdriver absorbs the abuse and is still perfectly usable as a screwdriver afterwards, did I "break" the screwdriver?

Or, am I misunderstanding how the word "breaking" is being used here? Is there a meaning I'm not getting?

Re:How Kubernetes Broke Git by jml78 on Sunday July 31, 2022 @12:58PM (#32296884)
Ok, tell me the tool they could use instead of git to handle and overcome the type of organization and technical they are experiencing
Re:How Kubernetes Broke Git by Karellen on Sunday July 31, 2022 @04:05PM (#32298316)
Huh? What has that got to do with whether or not they broke git?