https://cursor.com/en-US/blog/git-at-any-scale to avoid automatic translations (couldn't find a button to switch)
Git at any scale
21–30 of 128 posts
Re: Git at any scale
#22That was a very well written and interesting article. I really enjoyed it. Some good background for people telling GitHub to "just scale".
Re: Git at any scale
#23I don’t see a button to switch to English and the German text is a pain to read, comparable to Reddit auto translate..
Re: Git at any scale
#24Re: Git at any scale
#25Re: Git at any scale
#26Re: Git at any scale
#27Re: Git at any scale
#28It’s hard to overstate the reputation of the author of this post. Everything good about GitHub’s internal systems seemed to have his name all over it (I realize that today this statement hits different than a few years ago). Our times at GH didn’t overlap much but hearing the fact that he’s working at cursor increases my estimation of their engineering org by leaps and bounds.
[flagged]
Re: Git at any scale
#29When I've worked at big companies they had bespoke SCM that resolved this. But i'm curious about mid size teams that are big enough to overwhelm git but not so that they can rewrite it.
Re: Git at any scale
#30how does git lock the repo on extreme concurrency? let's say 1000 devs writing to the same repository? eventually you'll have saturation of the resource locking everyone out. When I've worked at big companies they had bespoke SCM that resolved this. But i'm curious about mid size teams that are big enough to overwhelm git but not so that they can rewrite it.
The problems start when there is a lot of changes on one branch and usually the first band-aid is to put a commit queue in place. The few very big companies that need even more than that probably aren't going to put their code on a new git hosting provider tomorrow.