Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

SVN hosting

Discussion in 'General Discussion' started by Bankler, Oct 4, 2016.

  1. mysticfall

    mysticfall

    Joined:
    Aug 9, 2016
    Posts:
    649
    I guess it might have something to do with a branching policy each projects use also. My personal experience matches what @snacktime has said though.

    When it comes to managing brances, I don't think there are any features that Svn provides which Git lacks which means you can use Git like Svn if you want. Probably only real advantage that Svn has over Git could be the fact that it's simpler to learn due to its non-decentralized nature, in my opinion.

    On the otherhand, the latter provides so many useful features that the former doesn't have, like its ability to change history at will, stash local changes, and etc. And Git has many important improvements over Svn too, such as its capability to track renamed or moved files, more powerful ignore list syntax, built-in bisect feature, and more.

    With Git, I can easily create a local branch for every issue I work on, and if I need to switch tasks I can easily do that by stashing local changes or make a temporary commit to clean up later. And I can freely refactor directory and file structures without worrying about losing all the history (EDIT: it seems that a similar feature has very recently been added to Svn after so many years).

    I believe such extra features are what has made Git to be so popular despite its added complexity.
     
    Last edited: Oct 9, 2017
    angrypenguin likes this.
  2. JamesArndt

    JamesArndt

    Unity Technologies

    Joined:
    Dec 1, 2009
    Posts:
    2,913
    Several of the studios I have worked at in recent years either use SVN or Perforce. It's still a huge player in studios today because it's easy to use for teams, especially artists. Sure the engineering side probably prefers GIT or something else, but it's gotta work for everyone.
     
  3. cyberpunk

    cyberpunk

    Joined:
    Mar 20, 2013
    Posts:
    226
    I stuck with SVN for a while simply because the GUI tools were much more mature and the only way to use git was via command line. Now that has changed, there are GUI tools for git and many IDEs even have built in support. While as a single dev, SVN would probably suffice, I do think git has some advantages, for example cherry picking commits or stashing, so I just use git now.
     
  4. Bankler

    Bankler

    Joined:
    Apr 10, 2012
    Posts:
    66
    Again, this thread is dedicated to SVN providers and what alternatives there are. There are already tons of threads on the Internetz that brings up pros and cons between git/svn/mercurial/perforce etc.

    Regarding Deveo: For clarity, when Perforce (i.e the company "Perforce") acquired Deveo, they didn't change the technology. You can still use SVN just as before.