For a while now, I’ve been trying Pulse to manage my Eclipse installs across multiple computers. I’ve had significant, but not critical, issues in other areas that I won’t go into here, but because I’ve got a few active projects on my plate, I didn’t want to take the time to rebuild my entire Eclipse installation. On the flight, though, the camel’s back was broken.
The only way to open an Eclipse install that is managed by Pulse is to run the “Pulse Launcher”. The “Pulse Launcher”, though, checks for updates and looks up your profile online. Now, in Pulse’s defense, I knew all of this. I just assumed that, in the absence of an internet connection, Pulse would do the right thing and just launch the local profile as it existed the last time I ran it.
Suffice to say that it doesn’t. I was left sitting on a plane with work to do that I couldn’t do in my preferred IDE. Not good. Local software, even applications that have an online component, should be available offline. Period.
To be fair, a new version of Pulse was recently released. Maybe an offline capability has been added, but now I may never bother to find out.