Surprise, surprise!
A few days earlier than expected, the brand-new MacBook White showed up at my doorstep.
For those of you who have been following this saga, I’ve mentioned on a few occasions (even publicly) about my lack of enthusiasm for the progression of the MacBook product line, particularly with regard to the noticeable gap in the line for the developer/’warrior sub-notebook class.
Well, as my 12″ PB continues to slow down with the ever-increasing dev and communications load I place on it, I finally decided that it was time to upgrade. There are a variety of concerns that I have about the transition, including ensuring clean and viable content relocations from the PowerBook to the MacBook White, but obviously I will have to handle those as they arise… 
For several years, I’ve resisted having fully-defined rigs ready to roll out on Macs, mostly because I never replaced a Mac with a newer model until now. After all, I defined specific functions for each of the Macs I’d acquired, with a minimal amount of overlap. While the Mac Pro, for instance, is certainly capable of running all of the apps that are present on the other Macs, but it is a stationary workstation, not a notebook or mobile device. In a similar vein, the iPod touch is a spot-to-spot travel companion to manage real-time and near-real-time events, along with some quick decision making features that I would not use on the other machines.
But now, the new scenario of shifting almost all of the functions I typically use on the 12″ PB has finally come, and it’s time to begin the exodus. 
N.B.
Other related Javamancy posts (in reverse chronological order):
