3 ms·
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
by jwildeboer 4y ago
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.
- mdaniel 4y agoAs 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
- thrashh 4y agoI 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
- ec109685 4y agoGitHub 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.
- mikl 4y agoIt’s just clickbait, the author posts clickbait on here regularly. It works, unfortunately.