Dropbox is a cloud storage solution, equipped with features that help users to save time, improve productivity, and collaborate with others. Users can edit PDFs, share videos, sign documents, and collaborate with stakeholders without leaving Dropbox.
If I need a specific file or want to access certain movies or music tracks, I download and store it on one device (e.g., PC), where DB is integrated into the file system. I can then effortlessly access this file on any device, like a tablet, where DB is integrated into the file system.
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’d like to be able to hover over an image/document and have it expand/enlarge without actually opening it
I’d love to see a carousel that lets me thumb through more quickly
I’m almost always in thumbnail view. I’d like to see them re-organize automatically when something is moved or deleted instead of leaving an empty space.
Dropbox is a user-friendly, easy tool which requires little to no skill and they offer a free version with a good amount of storage available. There are other file sharing tools available however at a cost. Dropbox free version I have used for years and it serves every purpose I need.
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.
Because the program is simpler, it does not use large resources to run, and there are no problems on older operating systems. It is easy to use for both private and business use. It's a bit annoying that the same texts have to be rewritten multiple times. Consider whether you want the truth or for users to actually answer quickly and easily.
Dropbox is really useful, you can access any file from anywhere and you can upload and even edit files online, but, sometimes it can be slow. Downloading, uploading, and syncing is a bit slow, it can take several minutes. Furthermore, the search engine for large amounts of data can be slow too and it is not powerful.
They immediately responded like in an example that I gave where one of our staff members accidentally deleted the whole Special Hope Network Dropbox, we immediately contacted Dropbox they walked us through the steps of how to retrieve the information and luckily enough we were able to retrieve the entire Dropbox and we have had back and forth with Dropbox on what to do when an employee leaves how to remove them how to add another employee.
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 did not personally take any training for Dropbox so I am self taught but I know when our Vice President selected Dropbox, he personally did do some training modules on it and I'm assuming it was very easy and simple to understand since he now acts like he is a pro at it!
I needed to stay current in improving my daily operations. Dropbox was suggested to me by a former colleague two-years ago and I've been using it just fine ever since.
Dropbox stands out for its simple interface, reliable file syncing, and strong version history compared to other storage platforms. While Google Drive is better for real-time collaboration and OneDrive integrates well with Microsoft Office, Dropbox offers faster file sharing, better organization, and smoother cross-platform access. We chose Dropbox because it’s easy to use, works across different devices, and keeps our files secure and accessible.
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.
Being a small business, the pricing is a little steep for my organisation, specially when it's not directly reimbursable to my clients. But the confidence of being able to access all my years of work in a few clicks saves me huge amounts of stress and effort. It's true power comes to light when an unfortunate incident causes panic about probable loss of access to valuable data. It is delightful when it gets resolved without breaking a sweat. Hence, I would say that it is eventually worth every penny.
I am a designer, and I like to create a lot of options for my work. Each of these options is a potential asset which can be potentially monetised directly, or at a future date. Hence, being able to retrieve it at the right time is priceless.
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.
