I had a free coupon for some music on iTunes that I was interested in, and having spent more time then I’m comfortable with trying to get iTunes to take less memory then an entire installation of of Vista, I’m reminded of one of my favourite XKCD comics:
I’d still like to know what iTunes is doing with over 640MB of memory, 20% of a quad core 2.4GHz CPU (yes, that’s almost 2GHz devoted entirely to iTunes) since it’s too busy to redraw the screen properly.
This post is just a quick thank-you to Seagate for making the warranty return process simple and easy.
I have a ton of drives spread across my various servers and computers and have more or less standarized on Seagate drives, mainly due to the fact that they’re reasonably priced, perform better then the competition (at least when I’ve tested) and have the best warranty in their class.
Warranties are always up in the air though, they’re only as worthwhile as the company backing the warranty request. I finally had a drive reporting errors, my first in many moons, so I contacted Seagate for warranty.
Starting the process was simple, I used Google to look for Seagate Warranty, supplied the model and serial number, my contact information, put the drive in a box and shipped it off.
Here we are about two weeks later and I have a refurbished drive. According to S.M.A.R.T. the drive is brand new, although it’s not impossible for Seagate to reset the hours-of-operation counter before shipping the drive out.
So thanks Seagate for standing by your products! I’m ordering two more drives and you can get that they too will be Seagate.
Dear Apple,
I am currently running an entire virtual instance of Windows Vista (you know, that OS you keep poking holes at in your commercials) and in that instance I am running three different webbrowsers and a mail *server*.
Guess what is using more memory, iTunes or Vista? Now keep in mind one is an operating system and the other is an overgrown music player which Apple has bundled (hmm, wasn’t Apple among those crying about Microsoft’s bundling a couple years ago) with some of their hardware.
Please learn to write more compact code, and for the sake of all that is holy, learn how to use multiple threads so the entire iTunes GUI can be snappy and responsive while it takes iTunes 99% of a 2.4GHz core for over 30 seconds just to connect to an iPhone, will ya?
