As a developer, I’m pretty picky about my tools. The old debate about whether ’tis better to use a plain text editor or a full-fledged Integrated Desktop Environment was settled for me long ago; quite simply, I spend too much time with my head in code to do everything manually, as a plain text editor would require. No, I have very specific requirements of my editing environment, which is where I spend the greater portion of my day: I need code-folding, brace-matching, an outline of properties/methods…
Early on I was a huge fan of the Eclipse development environment. Eclipse, it seemed, sought to be the swiss army knife of dev tools; though it was primarily intended for Java, it’s plugin architecture allowed it to be extended to develop in any language a plugin was provided for. This allowed me to use one application to write in multiple languages and idioms, which was just fine by me. Since the majority of my work is LAMP-related (Linux, Apache, MySQL and PHP/Perl), I found that Eclipse coupled with the PHPEclipse plugin was perfectly suited to the way I write code.
But the PHPEclipse plugin had issues, as I was soon to find out. The version of Eclipse in the Debian and Ubuntu repositories is old, and the PHPEclipse plugin has some issues working on these platforms. This was fine when I used WindowsXP as my primary Desktop OS, but when I started using Linux on the desktop this stopped me in my tracks. And while there are some fine environments out there for the Linux platform, I missed the ease and familiarity of my Eclipse interface.
Aptana, installed as an Eclipse plugin, works on both Windows and Ubuntu-another selling point for me. I run a dual boot system, and any opportunity to use the same software on both sides of my box is welcome.