Need advice about which tool to choose?Ask the StackShare community!

Gitless

4
15
+ 1
0
SVN (Subversion)

726
548
+ 1
41
Add tool

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.

Decisions about Gitless and SVN (Subversion)
Kamaldeep Singh

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.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Gitless
Pros of SVN (Subversion)
    Be the first to leave a pro
    • 19
      Easy to use
    • 13
      Simple code versioning
    • 4
      User/Access Management
    • 3
      Complicated code versionioning by Subversion
    • 2
      Free

    Sign up to add or upvote prosMake informed product decisions

    Cons of Gitless
    Cons of SVN (Subversion)
      Be the first to leave a con
      • 6
        Branching and tagging use tons of disk space

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      What is Gitless?

      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)?

      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.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use Gitless?
      What companies use SVN (Subversion)?
      See which teams inside your own company are using Gitless or SVN (Subversion).
      Sign up for Private StackShareLearn More

      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

      What are some alternatives to Gitless and SVN (Subversion)?
      Git
      Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
      Mercurial
      Mercurial is dedicated to speed and efficiency with a sane user interface. It is written in Python. Mercurial's implementation and data structures are designed to be fast. You can generate diffs between revisions, or jump back in time within seconds.
      DVC
      It is an open-source Version Control System for data science and machine learning projects. It is designed to handle large files, data sets, machine learning models, and metrics as well as code.
      Plastic SCM
      Plastic SCM is a distributed version control designed for big projects. It excels on branching and merging, graphical user interfaces, and can also deal with large files and even file-locking (great for game devs). It includes "semantic" features like refactor detection to ease diffing complex refactors.
      Magit
      It is an interface to the version control system Git, implemented as an Emacs package. It aspires to be a complete Git porcelain. While we cannot (yet) claim that it wraps and improves upon each and every Git command, it is complete enough to allow even experienced Git users to perform almost all of their daily version control tasks directly from within Emacs. While many fine Git clients exist, only deserve to be called porcelains.
      See all alternatives