2 ms·
>TFVC would have scaled just fine is pretty contradicting to >TFVC like CSV/SVN has a harder time branching because it is branch-as-path/copy-on-write, for on
by trhway 8y ago
>TFVC would have scaled just fine
is pretty contradicting to
>TFVC like CSV/SVN has a harder time branching because it is branch-as-path/copy-on-write, for one instance. Scaling a repo that size requires intricate lock systems which TFVC supports
heavy branching and locks is exactly the things which make system less scalable, in all dimensions like devs number, repo size, parallel product versions being developed etc.
>Windows developers wanted git for many of the reasons that most of us use git: cheap branching, distributed/lock-free code development, etc.
exactly my point - they hit scalability limits of TFVC. You just said it using different words. We all using Git because it is [architecturally] the most scalable VC out there (i did development of a major [back then] VC almost 2 decades ago - we were starting to develop bunch of ideas back then which ultimately came out to the wide public in git)
- WorldMaker 8y ago> heavy branching and locks is exactly the things which make system less scalable, in all dimensions like devs number, repo size, parallel product versions being developed etc. It's not a contradiction. Those things scaled just fine for decades of software development. They aren't "nice", aren't "fun", but they are a scaling solution. The Windows team used Source Depot ("Perforce") for something like 30+ years, at the scale of the Windows team. There are companies and repositories in the wild in Fortune Xty companies with equally old, equally "scaled" repositories in classic, ugly centralized lock-based repositories. You and I may not want to work on any of those repositories, but they absolutely scaled in historic fact for a scale that still dwarfs the lifespan of git. You may confusing workflow flexibility with scalability? Command-and-control workflows are very scalable, but not very flexible. Distributed workflows are very scalable, and very flexible, when built right. The Windows team wanted a break from classic Waterfall and Command-and-Control workflows. They knew how to scale those and had scaled them successfully for many years. They used the change in source control as an opportunity to change workflows. TFVC could have done the job if they still wanted that workflow (presumably better than the hodgepodge of very old Perforce code and Perl scripts that was Source Depot, that had "scaled" for decades). There are still companies and developers happy with that workflow. The interesting part is that Microsoft wanted "something like git", that enabled those new workflows, but that scaled to what they were already doing in centralized repositories with Windows. Instead of investing in a Distributed-TFS, they decided to just use git, and they put a lot of effort into performance tuning to git which was contributed upstream and which we are all benefiting from now. Yes, they also built a simple optional plugin (GVFS) that is itself open source, and built on simple open REST standards. It's pretty much the exact opposite of building "their own Clearcase" or whatever; they didn't build a D-TFVC for their needs, they contributed directly to the open source one in an open way, exactly as you would want them to.
- dragonwriter 8y ago> Those things scaled just fine for decades of software development. There is a difference between “were used at scale because there were no known alternatives” and “scaled just fine”, and I think the facts in this case favor the former over the latter.
- WorldMaker 8y agoThe argument is that "scale" is related to quantity in this discussion, not quality. I agree that quality of life is better now with distributed VCS (whether or not a historic alternative existed, which is orthogonal to the discussion at hand), but "scaled just fine" is not a quality judgment on my part in that statement you pull quoted, it is an acknowledgement that quantity was handled appropriately.
- spiralx 8y agoSomething this article goes into in more detail with regards to Git: https://blogs.msdn.microsoft.com/devops/2017/05/30/optimizing-git-beyond-gvfs/ https://blogs.msdn.microsoft.com/devops/2017/05/30/optimizin...
- trhway 8y ago>You may confusing workflow flexibility with scalability? when increasing of scale results in cumbersome jumps through the hoops added to the workflow or the otherwise working workflows become impossible at all - that is a scalability problem. Git's easy branching and multi-repo (local repos) based workflows approach was produced as the solution to the scalability problems of central repository and lock based systems.