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.
I think this service works very well for me, but I have been a Verizon customer for almost 15 years. If you are someone who hops carriers it may not be the best fit. I also like that you can easily use it with all of your employees regardless if they prefer Android or Apple phones. (Whereas using Apple's or Google's services may not work seamlessly for all phones.) I think it still has room for improvement, and sometimes I worry about the longevity of utilization due to the nature of cell phone carriers constantly changing prices, plans, and every option under the sun to make a buck that we could be very screwed in the future if Verizon does something stupid (because historically, they all have)
The home screen shows a little bit of everything, but being a control freak, I would like to be able to customize it. (Granted, it would most likely have most of the same elements, but, for example, I don't need photos scrolling across the top. I'd rather have buttons like quick links to jump directly to what I want or to see a further bird's eye view of the content.
I like receiving notifications that a back-up is complete, but I would like to be able to set what other notifications are and aren't allowed to push to my phone.
I have set Verizon Cloud to back up on wifi OR using the data network. But if you are using wifi while doing a content restore and you lose that connection, either by leaving the building or the local wifi dropping out momentarily, the entire content restore will stop and need to be restarted. This can be very frustrating.
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.
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.
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.
All of the others provide more free storage. Verizon should out best or at least equal the best when you are already a Verizon data subscriber. It seems that by not doing this that they want to "nickle-and-dime" their already loyal customer base
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.
Thus far is has been a positive experience, and has saved a lot of man hours of both employees who replaced their phones to the IT department trying to help them put everything back no longer needs to go through a lengthy process.
The cost of this option is a bit higher than I'd like. I think Verizon is a little too proud of a product that every company is now starting to offer.
There is a free version with limited space, so at least trying it out to see how it will fit with your needs isn't much of a risk.
