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.
NetBeans is extremely user friendly and easy to start developing complex applications. Adding and configuring external libraries is much simpler than in Eclipse. It is highly cost effective and most of the latest framework based libraries required are automatically downloaded to the projects. The overall tool is also light weight and consumes less memory as compared to other competitor tools.
NetBeans [should] work smoothly with systems having less RAM. Systems with less RAM face trouble with NetBeans.
File open history also requires improvement. Once NetBeans is restarted, all files are closed automatically and there is no shortcut to open last opened files.
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.
Netbeans enhances my coding work, shows me where I have errors and helps find variable instances. I would be lost without find/replace in projects functionality as I use projects as templates for new projects. Occasionally the code hints aggravate me, but I understand that it is actually making me a better coder, working to get the 'green light' of a clean file with no errors or clumsy code.
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.
NetBeans has a very strong user community. We can find solutions here for almost all the problems we face. In addition, we can forward NetBeans Support teams the problems we cannot solve. We can get quick feedback from the support teams, but I generally try to solve my problems by following the forums.
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.
It works very smoothly as compared to other tools . The problem of restarting and reimporting the projects is not in the netbeans IDE . The front end development features are good . Netbeans connector is one of the best thing which enables us to deeply integrate netbeans IDE with google chrome browser
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.
By working on Netbeans I just learned one more tool and can teach others about it. One should learn every tool so that it might help someday if another editor is not available and you have to use different software for your work.
Compiling code became easy as it is not a feature of normal text editors. Only IDE can do this.
