The reason I got into all this “trouble” with the blog layout is because Movable Type 4 (the collection of scripts from SixApart that I used to create and maintain this blog) was too smart. Too smart for my own good, really.
If I hadn’t been poking around at CSS—in particular, the structural/layout aspects of it—I wouldn’t have recovered anywhere near as fast as I did. And while it was much easier to get up and running than previous versions, there’s still so much lacking in web apps that it sends me scurrying back to the comfort of native-application bliss (as always, I’m using ecto as my blogging editor).
I’m biased here, but that doesn’t mean I can’t objectively (and subjectively) justify myself when it comes to native applications. I avoid doing any form of creation within a web page if I can help it. Lots of people trundle along quite happily using LiveJournal (EL-JAY! ugh) or TypePad or Blogger or—eek!—MySpace, typing their blog entries into a web form and clicking that Submit button.
But all you have to do is click the wrong button once, or worse, go visit another website while you’re in the midst of writing a blog entry totally forgetting that to leave the page often times means losing the contents of that page.
So here I sit on BART (the train, not the man) typing away. Yes, I have an internet connection, but I’m not sure I’ll finish this entry (you know how I get) before it’s time to disembark at Union City for my weekly visit to the Korean Herb Doctor. Yes, I could close the MacBook Pro and when I opened it later, the webpage would likely be there, but perhaps not. Perhaps Safari will try to connect to the web before I have a chance to reestablish an internet connection and its display of an error message will be enough to lose whatever I type. Probably not, but the best software is that which removes doubt from the proceedings and provides a sunny path to your goals.
Which brings me to Amazon MP3. Yuck.
I tried. I really did. I spent a half hour trudging through the site in search of my old standbys. I was fully prepared to shell out the $8.99 or whatever to repurchase an album I already had just to compare things.
Well, there’s two million songs, and then there’s two millions songs you’d bother with. In searches for “Billy Joel”, I ended up with cover-band albums and tribute albums, and even some weird Asian group of tweens listed only by their Americanized first names. Among Kay and Bobby and Tom was a boy called “Billy Joel”. The sad part is that it was better than most of the alternative listings which were primarily karaoke tracks. At least the kids were singing original material.
Searching for other well-established artists turned up similiar disappointments. I finally ended up with an older Sufjan Stevens album, “Illinoise”, but not after downloading an ironic client application which was required for downloading an entire album at a time.
The client application was the best part of the experience, though. After downloading that and installing it—which required quitting Safari and relaunching it—the purchase started a download of a .amz file, which was the album’s bundle of resources: artwork, songs encoded as MP3s, but at 256kbps and with no DRM.
iTunes Store songs are encoded as AACs (MPEG-4) at 128kbps. Don’t go thinking that the Amazon downloads are twice as nice because they’re encoded at a higher bit-rate because AAC is a much more efficient codec than MP3.
You also end up with a song file that’s 60% larger than an iTunes song of a similar length. That means that if your iPod normally can hold 10,000 songs from iTunes (or your own CDs encoded with AAC), it can only hold 6,250 Amazon MP3 songs. If your iPod is a classic or “classic” iPod with a hard disk, that also means significantly poorer battery life because the hard disk has to spin up more often to access the larger song files.
But I saved a whole $1.00 and the music I have has no technical restrictions on copying as much as I want. But then, I have yet to bump my head against the technological restrictions of the FairPlay (iTunes) DRM, so that doesn’t mean anything.
What a chore. I suppose they’ll get better, but then so will iTunes. Yes, I’m once again biased, but my biases are out in the open.
At the end of the day, that half hour could have been better spent—on fixing the CSS & HTML of this blog, for instance—and I’ll take the comfort of a ⌘S and a local file anyday.