Need advice about which tool to choose?Ask the StackShare community!
Gitless vs SVN (Subversion): What are the differences?
What is Gitless? An experimental version control system built on top of Git. Gitless is an experiment to see what happens if you put a simple veneer on an app that changes the underlying concepts. Because Gitless is implemented on top of Git (could be considered what Git pros call a "porcelain" of Git), you can always fall back on Git.
What is SVN (Subversion)? Enterprise-class centralized version control for the masses. Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
Gitless and SVN (Subversion) can be categorized as "Version Control System" tools.
Gitless and SVN (Subversion) are both open source tools. It seems that Gitless with 1.44K GitHub stars and 76 forks on GitHub has more adoption than SVN (Subversion) with 327 GitHub stars and 120 GitHub forks.
SVN is much simpler than git for the simple stuff (checking in files and updating them when everyone's online), and much more complex than git for the complicated stuff (branching and merging). Or put another way, git's learning curve is steep up front, and then increases moderately as you do weird things; SVN's learning curve is very shallow up front and then increases rapidly.
If you're storing large files, if you're not branching, if you're not storing source code, and if your team is happy with SVN and the workflow you have, I'd say you should stay on SVN.
If you're writing source code with a relatively modern development practice (developers doing local builds and tests, pre-commit code reviews, preferably automated testing, preferably some amount of open-source code), you should move to git for two reasons: first, this style of working inherently requires frequent branching and merging, and second, your ability to interact with outside projects is easier if you're all comfortable with git instead of snapshotting the outside project into SVN.
Pros of Gitless
Pros of SVN (Subversion)
- Easy to use20
- Simple code versioning13
- User/Access Management5
- Complicated code versionioning by Subversion3
- Free2
Sign up to add or upvote prosMake informed product decisions
Cons of Gitless
Cons of SVN (Subversion)
- Branching and tagging use tons of disk space7
Sign up to add or upvote consMake informed product decisions
What is Gitless?
What is SVN (Subversion)?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Gitless?
What companies use SVN (Subversion)?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Gitless?
What tools integrate with SVN (Subversion)?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7