There's been a fair bit of talk about PHP IDE's of late. That's not surprising given how useful they can be. (Really, folks, vi can only take you so far.) Most of the attention has been focused on the big boys: Eclipse and its derivatives (both free and commercial), Komodo, and NetBeans. Eclipse and NetBeans are both Java based, and Komodo is based on Mozilla's XUL platform (which also runs Firefox and company). I've been bouncing between them for a while, and haven't really been satisfied with any of them. I usually refer to Eclipse as the one I hate least. :-)
There's a new contender to keep an eye on, though, that is worthy of notice: KDevelop.
It's the little things that really make or break a system. For instance, earlier tonight a song came up on my playlist in Amarok. I realized the name was misspelled. I corrected the ID3 tag. I then went to the directory where the file was and renamed it. The song was still playing. Amarok noticed and rescanned my collection, updating its records of the new file name, and kept on playing the song without any interruption.
That is how a computer is supposed to behave. :-)
The great question of the day has been solved, and it is Emacs that wins.
Not that I use Emacs, mind you, but I've said for years that sooner or later, GNU/Linux would go away and be replaced by your choice of KDE/Linux (KDE having taken over so much functionality that all it needs is a kernel) and Emacs/Linux (Emacs already being almost an OS, except for missing a text editor). The only question was which would happen first.
Some people complain about how GNU/Linux isn't desktop-ready. It's too hard to use, the applications aren't there, it does things in silly and quirky ways... We've all heard the list. And some of us persevere anyway.
Recently, though, I've been working on-site with a client for a few weeks on a PHP project. The web app we are building is on a remote GNU/Linux server. Our desktops are all Windows XP SP2, of course. Because I need to edit the files locally but test them remotely, I need a fair bit of network transparency. Of course, Windows XP provides none unless everything is using SMB, which our production web server does not (naturally). So what setup did I have to cobble together?
So I finally bit the bullet and switched to KDE 3.4. Those who know me will know that I am a big fan of the KDE team's work, and every version has some compelling reason to make me upgrade. There are a couple of them this time around, although as always there's a few places that need some work.
My main desktop runs Debian Sid, the "Unstable" variant. Of course, in practice it's still fairly reliable despite the name. Things do get weird on occasion, but so far nothing show stopping. It's also reasonably up to date (usually more so than Gentoo stable but less so than Gentoo unstable, or masked, or whatever they call it), but KDE 3.4 has been delayed because Sarge, the current Testing version of Debian, is soon to go stable, and the fewer big changes there are in Debian right now the easier that will go. Fair enough, I suppose. Fortunately, the Debian-KDE team has made pre-release packages available for impatient folks like me. Thanks guys! Installation was fairly smooth, except that the kdelibs-data package wanted to overwrite a file owned by kplayer (a video player based on the mplayer engine, for those not familiar with it) and kplayer wouldn't uninstall until kdelibs-data was done installing. A quick Force Overwrite (a useful Jedi power) solved that, and I was soon staring at the new and improved KDE 3.4.