I very recently wrote a blog on how I felt about Snow Leopard, and my first impression with the OS. This is just an update to that post, so if you have not read it already, you may either ignore this post, or put it on hold while you read this.
One thing that I talked about was the apparent lack of Quicktime X, one of the innovations of the new OS that Apple touted the most at the World WIde Developers Conference. While it has suddenly appeared, and is indeed very nicely designed, it has some serious issues, surprise surprise. It seems Apple hasn’t done such a good job with the 64bit environment as I first gave them praise for, at least not yet, this might (and should) be fixed by the official release. Now the Quicktime player in and of itself is fully 64bit, there are no issues there, but it seems Apple has chosen to split up the processes, letting Quicktime handle the GUI and design, while a separate process, the QTKit Server, handles some of the more hardcore processing. When it turns out that the QTKit Server shows up as a “normal” 32bit process in the activity monitor, the alarm bells start wailing.
Come on Apple! You can do better than this! Or maybe there’s something I don’t understand, it’s not like I’ve done any research on this new thing, it might be that a 32bit process is necessary to play movie files that were made on a 32-bit processor, and therefore the QTKit needs to be 32bit for these movie files? I don’t think that sounds very reasonable, but it’s possible, and I will test the hypothesis some time in the future, I shall simply make a movie myself and see how Quicktime handles that, but for now I stand disappointed.
Edit: I googled a bit, and found an article suggesting that the QTKit is in an even worse shape than I thought… Read more about it here.
Song of the Blog: The Static Age
Sincerely yours
Bjørn
