Being free from the tyranny of Eclipse workspaces is, on its own, damn nice. If you're the type that likes your version control integrated in your IDE, SVN and

Being free from the tyranny of Eclipse workspaces is, on its own, damn nice. If you're the type that likes your version control integrated in your IDE, SVN and git feel much more natural in NetBeans than the Team Provider implementations in Eclipse. Eclipse requires navigating to the source control perspective, adding the repository, checking out, and then selecting the option to look for projects which you can open in your workspace.. its not exactly a smooth process. NB is more akin to what you'd do if your terminal was open. In terms of stability, NB definitely wins there. Never crashes and none of the typing slow downs that used to bug me [what seemed like] all the time in Eclipse. The one incredibly irritating thing about it is the way it forks processes when running via maven. Start an http server with netty and hit stop, the process is still running. I've taken to doing most of my testing from a terminal, which is a somewhat janky process I've forced myself to get used to.