Switching Rails IDE to Find Out NetBeans is Really Cool

I’ve been using Xcode 3 for my Ruby on Rails projects since learning the language because the tutorial I followed to learn the framework did the same.  Xcode was easy to use and had the basics of what I needed.  Keep my files organized.  Don’t slow me down with unnecessary steps or hard to find features.  Easy enough.

A few months back I searched to see what other IDEs people were using and NetBeans came up as a nice choice.  The price was right, free, thanks to Sun open sourcing the tool.  NetBeans built it’s rep on Java and many Rails developers seemed pleased with it.  I downloaded the product, installed it, and then like so many of my investigations I abandoned the task for some deadline or need to be productive.  After all, switching your IDE is a significant task.  Your productivity goes down as you learn the new actions and key strokes.  It’s like when you move to a new neighborhood.  It takes a while to figure out where to get the best take out, so you eat what is convenient for a while even if it’s not that good.

Fast forward to the present, I decided to create a new iPhone app to play around with location services.  I upgraded my iOS and that lead to an Xcode 4 upgrade, new provisioning, etc. etc. Many of you know this pain.  I spent more time futzing around than learning though in the end I did show a map of where I was on my phone.  I went back to my Rails project and that’s when I realized the hidden ramification of my pursuit.  Can you guess?

I had upgraded my development environment for Rails without really thinking about it.  Darn it! There goes my productivity as I learn the new tool that is actually a bit different from what I am used to.  Not one to sulk, OK I might have sulked a bit, I decided to use this as an excuse to dig into NetBean again. I am happy to say I am a NetBeans convert for sure! Here’s why.

First, getting my project up and running was simple.  I started a new project, selected the option to start my Rails project from existing source, and I was off and running.  NetBeans had inferred just about everything I would want from looking at my folders.  My database was linked.  My source code repository was hooked up.  Really, they did a good job of connecting the dots.

What’s more, the IDE offered a bunch of features I didn’t get in Xcode either because they were not there or not easy enough to find.  NetBeans treated my classes as objects adding extra navigation and functionality.  I liked the way Find worked.  My windows and tools were all integrated where as with Xcode I ended up creating a hodgepodge of applications including terminal for shell scripts, svnX for source code management, and others.

I realize of course that Xcode or Xcode 4 may have some or all of what I am already using in NetBeans.  But that’s the key point.  NetBeans got me there faster and without slowing my productivity that much.  Switching my IDE, while accidental, has actually lead to a richer set of tools in my toolbox.  I am almost ashamed to admit I didn’t look harder for these with Xcode.

For you Eclipse or Xcode 4 fans, please don’t take offense.  Selecting your IDE is really like picking a car.  You’re going to spend a lot of time with it and the overall experience matters as much as if it has features you want like integrated GPS and bluetooth, anti-lock breaks, or a sun roof.  I am sure I could be just as happy with these tools long-term as I expect to be with NetBeans.  But for now, I am smitten and comfortable driving the car I have.

The one piece of advice I would offer is you may want to consider learning Rails before moving to NetBeans.  NetBeans does so much for you that you might not learn the guts of the framework and how to really develop in Rails at the lowest levels.  For example, doing a migration from a dialog box is not the same as learning migrations at the command line and all the nuances that come with.  Still, if you are shopping for a new car, I mean a new IDE, I’d put NetBeans on your radar.

Cheers!