JasonOgrady
Latest
Mountain Lion: It's called a developer preview for a reason
Every time a developer preview of a new version of Mac OS X or iOS arrives, we at TUAW wait for the onslaught of emails telling us about the favorite apps that did or did not work, peripherals that suddenly won't work, or machines that end up being totally borked. Jason O'Grady at ZDNet has written a wonderful cautionary tale about what might happen if you pull the tail of Apple's OS X Mountain Lion. O'Grady installed OS X Mountain Lion DP1 on a backup 11" MacBook Air and basically loved the new OS and how well it worked with most of his existing apps. He was impressed with the integration of iOS capabilities and the improved security. And then all hell broke loose. While working with eBay client iSale on the MBA, things started going bad -- the app crashed repeatedly. So O'Grady decided to try a reboot ... which didn't work. To make a long story short, he "elected to take the "nuke and pave" option. I ended up booting from my Lion flash drive, reformatting the SSD and re-installing the relatively stable Mac OS 10.7 (non-Mountain) Lion. Patching it up and calling it a day." O'Grady ends the post with a reminder that all of us who are anxious to try out developer previews need to have pounded into our brains every time Apple tempts us with a new and shiny OS release -- don't install developer previews on production machines, and always assume that the worst will happen. As O'Grady found out, sometimes that worst possible case does happen and in this situation, you'll be mauled by an angry Mountain Lion.
iPad 2 launch: not Apple's finest hour
Jason O'Grady, writing for ZDNet's The Apple Core, penned an incisive piece on the five ways that Apple screwed up the iPad 2 launch. I agree with every point. Usually, Apple has been very good on getting information to the huddled masses waiting for the next new iThingy, but this time the company side-stepped the issue and let everyone fend for themselves, to the liking of no one. Here's what Apple got wrong: Not allowing pre-orders: Allowing potential customers to pre-order new products helps assure they can get the new stuff in their hands on day one. This time, not so much. There are plenty of reasons pre-orders might have been infeasible, including lack of inventory or a bad component delaying shipments. Still, in a perfect world, Apple should have taken the high road and allowed pre-orders, even if the number of units allocated was slim. No availability tracker: Apple has been good about providing information on in-store availability of new products. In the past, the company has put up a page (it no longer exists), providing a grid of what stores had particular models. This prevented the stress of going to your store and coming up empty. If you were in a populated area, with a few Apple stores, you were given alternatives. This time, no such information was provided.
