3 ms·

> I often wondered why Git is so difficult to learn, compared to other tools. Yes! This is something many people wonder -- other than those who love git :) I u

> I often wondered why Git is so difficult to learn, compared to other tools. Yes! This is something many people wonder -- other than those who love git :) I used to love Mercurial and I still mourn its mostly-loss. So I welcome a new DVCS system that is friendlier than git. > Diversion’s code is managed on Diversion! This is a good sign. > can synchronize with existing Git repositories (each new commit in Diversion goes into Git, and vice versa) Can you expand on what this means please? Does it simply mirror, or is it feature-for-feature compatible? Is it a backup capability? > still using legacy tools like SVN and Perforce I won't argue re SVN, but Perforce? It's used in the game industry primarily for its excellent handling of binaries / large binaries. How well does Diversion handle that kind of thing -- multigigabyte data sets, frequently changing? The site says large files are fine, but that's too vague for games, IMO. Large, frequently changing, binary-not-text hard-to-diff files? Edit: one final question: why cloud only? Why not software that can be locally hosted, or hosted by (other) service providers? What if I love Diversion and want to run a Diversion setup on my own Linux box in a cupboard?

4star3star 3y ago
The difficulty of git is that it can do so much in so many different ways. What's actually needed is something like a linter for git workflow, where an org can enforce an opinionated subset of git's capabilities in a prescribed order of operations.
sasham 3y ago
The Git sync feature allows one to import an existing git repo (currently GitHub is supported) into a new Diversion repo, and keep both in sync: every commit into Git is imported into Diversion and vice versa. This allows a member of a team that works with Git to try Diversion, to keep backups, and to use GitHub Actions or other CI tools that work with git.
sasham 3y ago
Perforce is amazingly scalable, but that comes with a price (literally and figuratively :)) We still can't handle petabyte repos like P4 does, but we'll get there. But we can handle very large and frequently changing binaries pretty well.
sasham 3y ago
Right now we're trying to get it to users who prefer something that just works, and don't want to think about hosting. But you can actually run Diversion in a container (that looses distributed storage and DBs, which means it won't be as scalable). Other providers would definitely be great, if we succeed in standardizing it like git.
- vintagedave 3y ago
  Thankyou for this (and the other!) replies, much appreciate your involvement in the thread! Answers like this also make me feel more confident / interested in the tech.

4star3star 3y ago

The difficulty of git is that it can do so much in so many different ways. What's actually needed is something like a linter for git workflow, where an org can enforce an opinionated subset of git's capabilities in a prescribed order of operations.

sasham 3y ago

The Git sync feature allows one to import an existing git repo (currently GitHub is supported) into a new Diversion repo, and keep both in sync: every commit into Git is imported into Diversion and vice versa. This allows a member of a team that works with Git to try Diversion, to keep backups, and to use GitHub Actions or other CI tools that work with git.

sasham 3y ago

Perforce is amazingly scalable, but that comes with a price (literally and figuratively :)) We still can't handle petabyte repos like P4 does, but we'll get there. But we can handle very large and frequently changing binaries pretty well.

sasham 3y ago

Right now we're trying to get it to users who prefer something that just works, and don't want to think about hosting. But you can actually run Diversion in a container (that looses distributed storage and DBs, which means it won't be as scalable). Other providers would definitely be great, if we succeed in standardizing it like git.

vintagedave 3y ago
Thankyou for this (and the other!) replies, much appreciate your involvement in the thread! Answers like this also make me feel more confident / interested in the tech.