> Git assumes that clients work offline and need a complete copy of the repository. Since nearly all of our clients are agents and jobs, we designed Scion’s client and protocols around a server that is always reachable, and have clients fetch data when they need it.
That sounds like Subversion with extra steps
> In git, you commit locally and then push to share your work. In Scion, every commit, rebase, or merge happens on the server, so there’s nothing to push,
Yep not beating the allegations with this one
To be fair 90% of the companies I've ever worked for always used git in a way that turned it into Subversion, but with 10x the storage usage (note: I hate Subversion with a passion, I'd rather send patches via email than that)
That sounds like Subversion with extra steps
> In git, you commit locally and then push to share your work. In Scion, every commit, rebase, or merge happens on the server, so there’s nothing to push,
Yep not beating the allegations with this one
To be fair 90% of the companies I've ever worked for always used git in a way that turned it into Subversion, but with 10x the storage usage (note: I hate Subversion with a passion, I'd rather send patches via email than that)