NB splash image

I love the fact that in the past 2 years, Netbeans have been the “most improved IDE” in the dwindling Java IDE market. Having said that, it’s also a minor annoyance to keep downlaoding the next stable release constantly. It seems like there is a new “release” every 10 days. I barely had a chance to take the wrapper off of 6.5 and now I see 6.5.1 is available. Jeeze. I’ll give them credit for having the sexiest splash startup though.

Famous last words I posted on twitter today, “been (surprisingly?) productive today. I’m going to finish ahead of schedule ” No sooner did I say that when Jetbrain’s IDEA started to flake on me (see above). At first I thought it was a disk issue (logs pointed to the vfs) , so I wasted an hour or 2 going down that path. Disk is fine OSX disc permissions are fine…etc. I’m looking at other possibilities but I do know that I don’t have to stop development since this a maven project that lives in our subversion repositoriy. This is the point where all the whining and  b**tching about doing things The Maven Way is silenced in favor of the pure joy of using a “standard” project structure . Both IDEA (as of 8.x)  and NetBeans can open Maven Projects as IDE projects with all the classpath info intact. So as I wait for the Netbeans 6.5.1 to download I know that I should be ok to pick up where I left off. If this had been in some IDE specific  project structure, this would have been a real pain in my@$$.

Peace,

GJ

Not to be outdone by IntelliJ IDEA with it’s very cool Dilbert plugin, Netbeans now has it’s own Dilbert strip plugin. I can not tell you how many times that little strip in IDEA has lightened my mood while as I am coding. That plugin has saved lives, kid.
Enjoy,
GJ

I wanted to choose between IDEA and Netbeans but I couldn’t. They both have great features that I need in my life right now. On the IntelliJ IDEA side, I’ve been bouncing back and forth between version 6 and the newest 7.0 milestone release. The only reason I haven’t completely switched is that 7.0 (codenamed Selena) is missing some of the 6.0 plugins that I really need (like SoapUI). 7.0 is a bigger leap forward in features than 5.x to 6.x was. So if you held off on getting 6, you might want to take a look at 7. On the Netbeans side, I’ve been using Netbeans 6.0M10 and I can finally stop b**tching about buggy milestones. Rather than piling on the latest gadgets, this release was all about improving the editor. They seemed to have taken a lot of hints from the way intelliJ IDEA editors work. The refactoring menu and some of the keyboard intentions are now very similar to IDEA. Hell, it’s no secret that Netbeans sees IDEA as the model for editing and refactoring. It’s been said often enough on the Java Posse. I wonder how the Ietbrains INtelliJ team feels about that? IDEA is still the best IDE for code writing but Netbeans 6.0 M10 shows that the gap is closing. Netbeans has always seemed to be the reference implementation of JEE 5 tooling in my opnion. Since they are supported by Sun directly, they get all the hot features first. So as I play with my first Jboss Seam apps, it’s Netbeans that I turn to. So for now I keep both IDEs open on different virtual desktops.
Laterz
GJ

© 2010 Ghetto Java Suffusion WordPress theme by Sayontan Sinha