How Kubernetes Broke Git

Re:How Kubernetes Broke Git by jwildeboer on Sunday July 31, 2022 @12:10PM (#32296521)

I’ve read the article 3 times now. I still fail to find the part where git broke. I also fail to find a concise explanation on what the solution is. I may need a beer to understand this.

[ Parent | on HN ]

Re:How Kubernetes Broke Git by mdaniel on Sunday July 31, 2022 @12:28PM (#32296647)

As best I can tell, the heart of the alleged issue is this from the middle:

> A system that could record atomic commits across projects or a better submodule experience would have allowed for more flexible developer organization, especially as the project grew to a new scale.

but otherwise I'm with you that this could have used a better title or something

[ Parent | on HN ]

Re:How Kubernetes Broke Git by thrashh on Sunday July 31, 2022 @02:03PM (#32297306)

I can’t tell if it’s because they had a good process and the tools didn’t fit or because they have a terrible process and nothing was going to work for them anyway

I see the latter much more often when I jump companies and Google’s projects have had terrible API stability so I’m not really sure Git is to blame here

[ Parent | on HN ]

Re:How Kubernetes Broke Git by ec109685 on Sunday July 31, 2022 @02:18PM (#32297435)

GitHub is the system that broke. All the communication systems within it needed to be disabled for custom notifications since it would otherwise be too noisy.

[ Parent | on HN ]

Re:How Kubernetes Broke Git by mikl on Sunday July 31, 2022 @02:36PM (#32297609)

It’s just clickbait, the author posts clickbait on here regularly. It works, unfortunately.

[ Parent | on HN ]