4 ms·

Most of the previous version control systems you mentioned were much less complex and had an extraordinadily easy mental model to understand in comparison. Git

Most of the previous version control systems you mentioned were much less complex and had an extraordinadily easy mental model to understand in comparison. Git set out to solve a different problem: adapt VCS to an agile, CI/CD world. It does this much better than those previous VCS generations, but its mental model does seem needlessly complex.

nijave 5y ago
Well, I think it was also meant to be highly distributed as well (many different people all over the place could then come back and bring their changes together) In order to achieve that, I think you end up with some additional complexity like local vs remote and a complicated graph structure to accommodate people coming "on" and "off" line
- unclebucknasty 5y ago
  >Well, I think it was also meant to be highly distributed as well Yeah, I guess I kind of consider that an agile tenet: in general, that people can work quickly and iteratively with limited interdependencies. Said another way, it would be difficult for teams to work in an agile fashion--where the work itself is frequently distributed and happening in parallel--using most older VCS models.
plorkyeran 5y ago
Git set out to solve the problems the Linux kernel development faced, which is not particularly "Agile" and doesn't do CI/CD.
- unclebucknasty 5y ago
  Point taken. May be more accurate to say that it solves some core common challenges that made it attractive for those later use cases. Main point being that comparing the complexity of Git and, say, SVN isn't apples to apples, as the former is suited to use cases that are inherently more complex.
- B1FF_PSUVM 5y ago
  > Git set out to solve the problems the Linux kernel development faced Which were "send patches to the maintainer", and a little bit of "work offline". Linus fixed those as needed, and people who haven't those problems are using his solution a bit like painful fashionable shoes - they hurt but dagnabbit, that's what the fashion is ...

nijave 5y ago

Well, I think it was also meant to be highly distributed as well (many different people all over the place could then come back and bring their changes together) In order to achieve that, I think you end up with some additional complexity like local vs remote and a complicated graph structure to accommodate people coming "on" and "off" line

unclebucknasty 5y ago
>Well, I think it was also meant to be highly distributed as well Yeah, I guess I kind of consider that an agile tenet: in general, that people can work quickly and iteratively with limited interdependencies. Said another way, it would be difficult for teams to work in an agile fashion--where the work itself is frequently distributed and happening in parallel--using most older VCS models.

plorkyeran 5y ago

Git set out to solve the problems the Linux kernel development faced, which is not particularly "Agile" and doesn't do CI/CD.

unclebucknasty 5y ago
Point taken. May be more accurate to say that it solves some core common challenges that made it attractive for those later use cases. Main point being that comparing the complexity of Git and, say, SVN isn't apples to apples, as the former is suited to use cases that are inherently more complex.
B1FF_PSUVM 5y ago
> Git set out to solve the problems the Linux kernel development faced Which were "send patches to the maintainer", and a little bit of "work offline". Linus fixed those as needed, and people who haven't those problems are using his solution a bit like painful fashionable shoes - they hurt but dagnabbit, that's what the fashion is ...