The majority of my academic and professional programming career has been spent writing code using an integrated development environment (IDE). I’ve dabbled with Eclipse, Microsoft Visual Studio, Macrodobe Dreamweaver, and various Borland products. Rather than juggle multiple text editors and source control consoles, I find it easier to stay organized using an IDE on large projects. When editing config files or writing scripts I prefer a lightweight text editor. In Linux, vi or gedit is my choice. Notepad2 is at the top of my Windows list.

A few months ago I decided to learn Ruby and the Ruby on Rails framework. I began with the obligatory Hello World program and quickly progressed through a series of tutorials using vi and gedit to get the job done. Since then, I’ve begun some larger projects and am quickly finding myself losing focus and missing the benefits of an IDE. Consulting Google, I compiled a list of prospective IDEs to begin my evaluation. I’m willing to give each of them a fair chance at becoming my Rails development environment, but have a few questions before I begin. What, if any, IDEs have I missed? How long should I try each one?

Needs (in order of importance):

1. Linux compatible
2. Project Browsing
3. SVN integration
4. Syntax Highlighting
5. Code Completion
6. Active Community
7. Unit Testing
8. Debugging
9. Auto-indent
10. Plugin support
11. Less than $100

The list:
*Each IDE/editor was capable of Project Browsing, Syntax Highlighting, and compatible with Linux.

1. Aptana RadRails
   Pros
   • Good SVN integration.
   • The latest Beta has working Code Completion.
   • Built on Eclipse.
   • More Rails features than Eclipse + DLTK.
   • Many plugins inherited from Eclipse
   • Free.
   Cons
   • Code Completion is broken in the current stable release.
   • Built on Eclipse.
2. Eclipse + DLTK
   Pros
   • SVN integration.
   • DLTK has Code Completion.
   • Tried and true.
   • Vast library of plugins.
   • Active community.
   • Free.
   Cons
   • Eclipse is slow and consumes a lot of memory.
3. FreeRIDE
   Pros
   • Auto-indenting.
   • Debugging.
   • Free.
   Cons
   • No SVN integration.
   • No Code Completion.
   • Performance could be an issue b/c it’s a native Ruby application.
4. gedit + plugins
   Pros
   • Lightweight.
   • Plugins.
   • Free.
   Cons
   • No SVN integration.
   • No Code Completion.
5. jEdit
   Pros
   • SVN integration.
   • Code Completion.
   • Plugins.
   • Free.
   Cons
   • Not user friendly.
6. IntelliJ IDEA 6.0
   Pros
   • SVN integration.
   • Code Completion.
   • Debugging.
   • Unit Testing.
   • Plugins.
   • Much more…
   Cons
   • $249.
7. Komodo IDE 4.1
   Pros
   • SVN integration.
   • Code Completion.
   • Debugging.
   • Built specifically for Ruby on Rails.
   • Much more…
   Cons
   • $295
8. Mondrian Ruby IDE
   Pros
   • Lightweight.
   • Free.
   Cons
   • No SVN integration.
   • No Code Completion.
   • Performance could be an issue b/c it’s a native Ruby application.
   • Spam in support forum.
9. NetBeans Beta 6.0 Milestone 10+
   Pros
   • SVN integration.
   • Code Completion.
   • Debugging.
   • Plugins.
   • Free.
   • Much more…
   Cons
   • Beta.
10. Ruby IDE from CodeGear
    Pros
    • CodeGear experience.
    Cons
    • Feature set not yet released.

I’ll be evaluating each of the IDEs/editors in turn and publishing my results as a series. Feel free to leave feedback and check back soon!

I purchased the Two-Disc Special Edition DVD of 300 from Wal-Mart this evening. Attached to the cover was a sticker that read “DOWNLOAD THIS MOVIE” and in small print, “Must reside in U.S. Windows Media Compatible Only. Not compatible with iPods.” Visiting walmart.com/300 in Firefox yielded the following:



It’s 2007. Why?

Last Sunday I purchased a Linksys NAS200 network attached storage (NAS) device and two Western Digital 500GB SATA drives hoping to solve my problem with backups and provide a shared storage solution for my home network. After a precursory examination of five NAS devices, I chose the Linksys NAS200 based upon its feature set, price, and the reputation of its predecessor, the Linksys NSLU2. The NAS200 boasts features such as:

• Ethernet connected storage.
• Dual SATA hard drive bays.
• Two USB 2.0 ports for extra storage.
• Internet FTP and HTTP access.
• Built-in media server.
• RAID 1 and 0 disk configuration.

Before buying this device I had been leaning heavily towards the D-Link DNS-323, but hoping the Linksys NAS200 would arrive on the market in time for my purchase. I mentioned previously that it was out of my character to buy bleeding edge hardware and I have to admit that I was a little nervous that the device would not work out of the box on my network. As a Linux user, I don’t think I’ll ever get over the anxiousness of buying new hardware.

The device was packaged well. The box pictured was merely a container for the much sturdier packaging material that housed the NAS200, a Quick Installation guide, CDROM, network cable, power supply, and some promotional material. I glanced briefly at the contents before proceeding to unhinge the plastic doors housing the NAS200’s drive bays. The doors were a little hard to open single-handed. Plastic clips found on either side of the doors must be pinched simultaneously to expose the bays.

Peering within the first bay, I was puzzled by the length of “ribbon” found inside. Not knowing what this was for, I consulted the manual located on the CD. To my surprise, the manual did not provide directions for hard drive installation. Printed on the edge of the ribbon was the word “Pull”. My wife giggled as she often does when she figures something out before me. The ribbons’ purpose is to aid in hard drive removal. Pulling the ribbon will eject the drive from its controller. Later, in the Quick Installation guide, I found a screenshot of the Setup Wizard depicting the ribbons proper use. Her assumption was correct. Reading the guide now, I’m impressed by the clarity of the screenshots found within. They are small, but readable.

With the drives installed, I placed the NAS200 on the shelf that was to become its new home. I then attached the device to my router with the provided Ethernet cable. You’ll need a longer cable if you plan on storing the device more than three feet from your router. I plugged in the AC adapter and turned on the device by pressing a small button located on the back panel near the AC input. The NAS200 chirped loudly signaling it had been turned on. The device’s internal speaker is loud and its tone is similar to that of a smoke detector. Some lights on the front of the device began blinking and the two that looked like disc platters lit up. At last I could turn on my computer.

Like the NAS200’s packaging, the CDROM was neatly branded. I didn’t have high hopes for running the Setup Wizard, but I did give it the college try. From the command line, I navigated to the CD and typed “wine Setup.exe” and cringed as several error messages appeared in my terminal. I didn’t bother going any further with this. Knowing the NAS200 would be assigned an IP address via DHCP from my router, I launched Firefox and navigated to http://192.168.1.102. I felt a small measure of relief watching the NAS200’s administrative page load within my browser. This feeling was soon found fleeting as I attempted to log in. The default username and password listed in the manual did not work. A few curses later, I remembered the default login (admin / admin) used by my Linksys router and gave that a try. It worked.

Feeling elated, I navigated through the remaining administration within minutes. I first chose “Firmware Upgrade” from the list of options. I was slightly disappointed when clicking “Check for Upgrade” opened a new browser window and directed me to the Linksys.com website. In the days of Web 2.0 you shouldn’t have to search for firmware updates and install them manually. Updates should download and install with one click. I found the NAS200 on Linksys’ website, but at the time of this writing no firmware updates had been published. Screenshots of the Linksys NAS200’s administration interface can be found below:

1,  2,  3,  4,  5,  6,  7,  8,  9,  10

Formatting the hard drives took little time. The “Disk Utility” section contained a set of simple controls for both drive formatting and the running and scheduling of Scandisk. I had prepared myself to wait at least a half hour for the formatting of two 500GB SATA drives, but only sat and watched the progress bar for about 5 minutes. Likewise, the “Disk Configuration” menu was also simple and configuring my device for RAID 1 mirroring was as easy as clicking a radio button. Soon after, my 1TB of raw storage became 465.29GB of mirrored drive space.

Once the drives were configured, I quickly changed the admin password and set a disk quota for guest users. Under “System Options”, I gave the device a more suitable name and assigned it a static IP address. I then created user accounts for myself and my wife. When creating user accounts, access to the device’s Download Manager can be set. I don’t remember reading about this feature within the product’s description before purchasing it. Not that I’m complaining, because the functionality is pretty cool. Basically it acts as an autonomous downloader. You provide the URLs, and it does the work. This single feature could end up saving money on my electric bill as I oftentimes leave my computer running all night to download large files. I don’t know the exact numbers, but I feel confident in saying that the Linksys NAS200 draws less power than my desktop PC.

To complete the installation I did a quick training session with my wife. She now knows to click Places -> Network within Gnome to find our network devices. Double-clicking “Thorbardin” (Yes, I was a Dungeon Master) displays her private folder and the public share entitled, “PUBLIC DISK”. Not being particularly fond of screaming caps, I tried to rename the folder, but was prompted with the following error message.

Unlike some other NAS devices, the Linksys NAS200 is quiet. I have to be standing within a foot of the device to hear any noise. The noise that does emanate from its internal fan is not of the jet engine variety. The fan within the NAS200 emits a low-pitched whir. I’m still quite impressed by this as my second story apartment is extremely hot. Its probably a good thing that the device has an operating temperature of 41 to 104ºF (5 to 40ºC). The surface of the NAS200 is not cool to the touch, but it is not particularly hot either. I can faintly feel air being pushed by the fan through the tiny holes dotting all sides of the device. That is a good sign.

I certainly feel more comfortable now that I have the Linksys NAS200 integrated into my backup strategy. With the NAS200 configured as RAID 1, I’ve all but eliminated the potential for single disk failure. My wife and I are already benefiting from the advantages of having a networked storage solution. We can finally share family pictures without the hassle of peer-to-peer file sharing between our computers. The NAS200’s product packaging and administration controls are both well designed and the device itself appears of exceptional quality. Any anxiety I had about the device communicating on my home network was unjustified. It works well with Linux and will undoubtedly perform just as well with Windows.