Apache Subversion is a version control option that is free to download and open source under the Apache 2.0 license.
N/A
GitHub
Score 9.1 out of 10
N/A
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
Toad Database Developer Tools
Score 8.8 out of 10
N/A
Toad by Quest is a database management toolset that database developers, administrators and data analysts use to simplify workflows, create code free from defects, automate frequent or repetitive processes, and minimize risks. Editions include Toad for Oracle, which automates administration tasks and helps proactively manage databases while embracing performance optimization and risk mitigation. Similar editions exist for IBM DB2, SQL Server, SAP, or MySQL and Postgres environments (Toad Edge).
After Microsoft Visual SourceSafe was discontinued, we chose Subversion and it was a great choice. We were able to migrate to Apache Subversion very quickly and easily and benefited immediately from its non-locking workflow (SourceSafe required users to "lock" the file when …
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 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 .
Before switching to GitHub we used Apache Subversion, but found GitHub was better in virtually every way. When we used subversion in 2011 (albeit things might have changed by now) creating and working on separate branches was tedious. We had to create a bunch of different …
GitHub compared to GitLab and Bitbucket seems to have an easier and nice to use interface. This is mainly due to the fact that GitHub is the No1 choice for most of the Open Source projects. Developers out there are already famaliar to it's UX/UI and use it every day.
Another …
Verified User
Team Lead
Chose GitHub
While SVN comes with basic functionalities, TFS is a superior tool and often unused to its potential in most cases. GitHub brings that equilibrium. It perfectly works like a versioning tool and can also be used to create CICD deployment pipelines.
Verified User
Engineer
Chose GitHub
The branches in Perforce and SVN are replicas instead of links/trees like in Github. Those two tools do not have rich APIs like that of GitHub. Subversion and Perforce do not support local repositories, which might hamper the development, if developer is coding and the tools …
We switched from Subversion to GitHub for two reasons. GitHub has better support built into our tools. Subversion was located on-premise and required us to maintain the infrastructure. GitHub is much easier to access from remote locations and we don't need to manage our own …
Others not listed above, CVS, Microsoft SourceSafe. GitHub offers the most comprehensive offering, including Code Review, Open API, Wiki (just to mention a few) in a single package. GitHub is likely the most used repository in the world. It's fast, even with high user volume. …
GitHub has better branching features than Subversion. The code review process in GitHub alone makes it worthwhile, whereas we could have branches in Subversion, it was missing the ability to comment and review other people's code before checkin. GitHub has more control around …
Github and git, in general, is much better than SVN or Subversion for version tracking and code collaboration. It takes the best parts of SVN and fixes a lot of what was broken with it. Github's own UI has evolved really well over time and they have taken developer productivity …
With the other version control software I've used, I've had a lot more hassles than GitHub. I have limited experience with SourceSafe but have used SVN a bit. I had a bit older version of SVN when I used it but you had to add files to SVN specifically for it to be committed. As …
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.
GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.
Toad for Oracle is very well suited for all Oracle implementations, be it single instance or RAC. It is best suited for use of Oracle DBA, Developer and Database Engineers. I don't recommend Toad for Oracle for Project Managers or Solution Architects. This can be a pricier choice for these people. They can do fine with free options like SQL Developer.
Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
Toad is a de-facto standard tool for data developers and analysts. Generally speaking it provides almost every function needed to manage data in EDW with great performance and stability.
The nature of clinical data is big-sized: one table may have billions of rows. Toad provides critical functions to manage SQLs, e.g. Top SQL that can monitor and manage SQLs using CPU power and network bandwidth, so that EDW administrator can optimize ETL operations in the best efficiency.
Many of our data analysts are not computer science backgrounded (having clinical / nursing background). Toad provides great auditing tools such as Tuning Lab or SQL Scanner, so that data analysts can train themselves with guidance of the tool.
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.
Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
The power and control it gives is at the same time kind of a negative thing. There's too many options available, even when you don't need them. For simple database operations it's sometimes easier to just use SQL Developer since navigation is way more intuitive and easy.
Related with the above: there is a steep learning curve. However, since this is the main tool for any Oracle developer, this is not that much of a problem.
If I remember well, Toad used to be free, some 20 years ago. Or at least had a free version. It would be nice to have a free version. The dedicated Oracle developers and DBA's won't use the free version, but all the rest of us developers might use it instead of SQL Developer. It would make communications between everybody somewhat easier.
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.
GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
I give is an 8 because nothing is a 10 and there is always room for improvement. I believe the user who is not as technologically inclined would be better suited with an easier way to identify the options for setting the layout up for Toad's GUI. To some it is very cumbersome and confusing.
There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.
I give the overall support for Toad for Oracle a 10/10. This is because whenever there has been an issue with this software, our team has got an immediate response. The same can not be said for similar software. The most recent example of this is when we needed to renew our licenses. Some employees were unable to log in to code with the given license key. Support was able to resolve the issue quickly.
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.
While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.
Toad is much better than Tableau query writer. Tableau is not intuitive and requires knowledge of proprietary database language to fully implement. Tableau does not perform as quickly and accurately as Toad. Toad is very easy and slim to install. Additional hardware is often required to run Tableau smoothly. Support for Tableau is even more expensive than Toad support.
Team collaboration significantly improved as everything is clearly logged and maintained.
Maintaining a good overview of items will be delivered wrt the roadmap for example.
Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.
Quick and easy query development helps reduce man-hours in a project which converts to real dollars.
Query analysis and tuning result in low database overhead and low latency, thus translating into real dollars because a system can thus handle more requests from customers.
Ease of use makes it easy to deploy greenhorns in projects with minimal training, thus helping save money. Otherwise menial and simple jobs would have required experienced DBAs.
