Out with the old, in with the new iTunes

iTunes11OK, the new iTunes came out yesterday, and – like just about everyone in the world – I downloaded and installed same.

After only a night and (part of) today, I can say this: Hey, it doesn’t suck!

I’ve long been a believer that iTunes has gotten bloated and begun its decline into sluggishness. It’s trying to be too many things to too many audiences: playing music, accessing iTunes store, synching iPhone or iPad and so on. This is a common refrain even among the Apple faithful, so don’t take this comment with a grain of salt.

I consider iTunes Apple’s to be the Mac company’s equivalent of Microsoft Outlook – a pig of a program that used to be so useful. (Side note: I bought a new computer – Windoze – about six months ago. I still haven’t set up any of the Office programs I purchased [the full boat], including Outlook. I’ve yet to miss any of these.)

Yet iTunes still works – and the new version is a better version of iTunes, unlike Outlook 2010, which is — to me — a steaming pile of crap compared to Outlook 2007.

Yet, at bottom, iTunes stills needs a total overhaul, but at least Apple appears to making an effort to release a better version of a troubled program, as compared to Microsoft: The geniuses at Redmond keep piling features/confusion on with each new release of Outlook.

That’s why I’m a little skeptical of articles like Farhad Manjoo’s Slate.com article titled (cleverly) Won’t Someone Take iTunes Out Back and Shoot It? Sure, he makes the same points I’ve made above, but without the grudging acknowledgement that this new iTunes is an improvement over the last. Yes, iTunes needs to die (but be replaced…how?), but it’s not in the cards to kill it right now.

I think that once the whole touch vs. desktop dust settles, there will be a more compelling reason to build a new codebase for iTunes (or two/three apps) that can be leveraged by all computing devices. Until that time, I don’t see a radical change in iTunes.

Update: I forgot to mention: What did iTunes cost you? Yeah, it’s free (yes, a revenue driver, but still).

Code Unfreeze

I put a code freeze in place at this domain because I transferred to a different host.

For the most part, I’m all done.

Got this blog transferred over (WordPress => WordPress, much better than a previous Blogger.com => WordPress move), got my CGIs in place (mainly my gallery) and have all CRON jobs pointing to new directories etc. on the new littleghost.com.


This was a lot more work than I had anticipated, but there were no deal-breakers. Just a lot of blood, sweat and swearing… Some things are still a little wonky, but – for the most part – I’m good to go.

FYI – I’m now hosting at ipower.com, and I’ve been pretty happy with them. I moved my other major domain, geistlinger.com to ipower.com a year or two ago, and was satisfied enough to move this domain. Their online chat, in particular, has been very helpful.


Code freeze

I’ve been in a code freeze mode lately, as I’ve been in the midst of moving my domain to a new host.

What a pain in the ass.

Moving the static HTML is trivial; the CGIs that I still have (yes, mock me! – but I don’t want link rot) were a little more challenging, and last – but not least – is the WordPress (my blog’s engine) transition.

The blog transition was a chore, but I’ve moved from a 2.x version to a 3.x version, and the updated WordPress is way more advanced (almost too advanced, but that’s another post).

Next: Actually transferring the domain from Host A to Host B (I have the new host set up under a different DNS).

Fun fun fun …..