Apache Subversion is a version control option that is free to download and open source under the Apache 2.0 license.
N/A
Git
Score 10.0 out of 10
N/A
N/A
N/A
Google Drive
Score 8.6 out of 10
N/A
Google Drive is a cloud file storage, synchronization, and collaboration platform and service, that features Google Docs, Sheets, and Slides for document editing and presentation.
$6
per month
Pricing
Apache Subversion
Git
Google Drive
Editions & Modules
No answers on this topic
No answers on this topic
Basic
$6.00
per month
Business
$12.00
per month
Enterprise
Contact Vendor for Quote
per month
Offerings
Pricing Offerings
Apache Subversion
Git
Google Drive
Free Trial
No
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
Discounts are available for students, educators, and non profit organizations.
Git is a newer version control system compared to that of svn. I think that svn is more stable, easy to learn/use, and not-so-complex as Git. Also, svn has very good client applications which provide extremely user-friendly user interfaces. Apache Subversion is also open source …
Git is probably the biggest open source rival to Subversion. It's designed for distributed development, an environment I'm not very familiar with. I've only got some experience with it, and only as a user, and even that is limited. I had some trouble wrapping my mind around the …
We used Visual SourceSafe before SVN many years ago and we chose SVN at that time mainly because it allowed us to do collaborative work on the same source code. It also had improved conflict resolution when doing code merges, blaming changes etc, which improved the speed of …
Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.
Git is better than Subversion in every aspect except that is not free . But since our company has bought Git licenses and I would not go back to using Subversion .
Git
Verified User
Engineer
Chose Git
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in …
Front-End Web Developer, Office of Mediated Education
Chose Git
The two main alternatives to Git that I know about are Mercurial and Subversion. I've never used either one, but I know a bit about Subversion. From what I remember, Subversion requires a server. I don't anyone using any other source control other than Git, it seems to have …
Git is more advanced and easier to use. It has a very simple UI and a very efficient command-line tool. Git gives you flexibility and performance for the price, and has greatly increased the complexity of workflow. The overall performance is good. It caches information locally …
GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria. GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way. G…
Compared to SVN, Git has a decentralized approach which increases collaboration in the team by enabling the local stored branches. There is no need to be connected to the repository(via an internet link) to work and commit code. Besides the fact that the performance of Git is …
I do not have much experience with other version control tools. Git is highly used everywhere and it is hard to find a development team that isn't using it. One thing I know is that with Git each developer has their own copy of a repository so they could technically work …
Git is the best Source Control Management Tool I've used. Every company, team, and project I've worked on professionally either used Git 100%, or was moving to Git, away from the alternatives like SVN. Git has all the features necessary, as well as a very large community of …
Git is by far the best version control system out there. It's open source, free, and fast. No other version control system I've ever used has had all three features.
Git is a distributed version control system. There is more flexibility to work with a bigger team. You can modify the same file and later merge all changes into a single file.
After using Subversion previously for a number of years, Git comes across as the new and improved source control approach. Git seems very suited to working with Agile:- branches can be created easily, allowing multiple developers to switch to them quickly, and having local …
Git is my favorite among all of the version control systems out there. It follows the Linux software philosophy of being built by many loosely coupled and small components that do one thing well. It's incredibly open, and its adoption in the open source community seems to be …
It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.
Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
It is possible to share files and folders with up to 200 email addresses, as well as with persons outside the company.Use the drop-down arrow to select who may see, comment on, or change the file or folder before sending out an invitation.I am very much impressed with this feature
Any user with access can store a file using different platforms like Android, IOS, Windows, or Ubuntu (Desktop version)
You can share files with any number of different users with different access rights or you can even keep it public by providing the access link and assign different rights for public access
You can open Excel/Word files using google software Sheets/Docs in the browser environment without having to install software like Microsoft Office etc on your Windows OS
Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.
Having a little bit more control and clarity over what is shared and how it is shared would be a useful improvement.
Could be more robust and flexible as far as assigning restrictions.
Google Sheets could be enhanced because Excel really is not there yet as a product with equal capabilities as there are still quite a few limitations to the functionality.
While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
It's perfect for me. It keeps things saved and is easy to remove items if needed. Also, I very much enjoy the formatting options. Along with the integrations it has for SSO. Overall, this is the most user friendly system I have ever come across.
It's easy enough to use for computer users of all ages and skill levels. I am an advanced user, and I think the hardest part might be showing someone how to download and set up the app on their device if they weren't too familiar with computers, but overall it is very easy to understand.
The documents load fairly quickly and also update in real time, especially given the fact that multiple people can be using it at once. The "Offline" feature works great to allow the user to make edits and access the document without access to the internet, and then sync changes later once they're back.
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
It takes a few days for customer support to get back to you. Although, I have not had to use support too often. Once you get an email back, they are very thorough and work hard to fix the problem quickly. It is a really great resource and a great way to get the help you need if you're stuck. A phone call also works quickly but you have to call during specific times.
The effective google workspace using training that my organization received and was conducted by me (as a team lead of the ICT team) was mind-blowing and as a result, our staff is performing well in terms of using the application for their daily jobs than before. Now, in my institution, all teachers and all the administrative personnel are very much interested in cloud storage facilities, in previous my institution was afraid of losing all important documents in the cloud storage. But, after having received the training they are now realized that if anyone has only one google account then he or she can use 15GB of cloud storage freely and they are now happy because now it is not necessary for anyone to carry the traditional pen drive.
It's an extremely easy software to implement, once you sign up for a google account you automatically have access to google drive with a set amount of storage space. The business or Google Suite accounts have more storage space than a regular free account, but setting up and accessing google drive is very easy in both cases
Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy. It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
In short, Google Drive is better for independent users who store a normal amount of stuff. OneDrive makes more sense for businesses and teams that are doing heavy-duty storage or large-scale syncing. Realistically, though, most users will fall somewhere in between the two, where either platform would meet their needs.
Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.