My Upgrade to Leopard
By now, you've seen many stories about upgrading to Leopard. Here's mine.
In the past, I would've slapped the DVD in, selected upgrade and prayed for the best. Now I'm older and (apparently) wiser. First, I cloned my hard drive with SuperDuper!. Then I attempted to upgrade. I started the process on Saturday morning and didn't check it until Saturday afternoon. At that point, I was greeted with the lovely blue screen of death. I didn't even bother to look up the problem - instead opting for the clean install.
The next time I checked (Sunday evening), the installation was completed. I registered, clicked through some stuff and started copying files from my backup drive. On Sunday night, I closed the lid on my laptop and haven't used it since. I guess new operating systems don't excite me as much as they used to. Then again, I do have two MacBooks, so I don't really need the Leoparded one.
As far as the lack of Java 6, that doesn't surprise or disappoint me. I'm sure it'll be out in a few weeks. By the time it's released, I doubt any of my clients will have made the leap from Java 5 -> Java 6.It could be that I'm burned out on technology - or it could be the Rockies and Broncos performance this past weekend has got me bummed. Who knows - the good news is there's lot of trick-or-treating to be done in the next couple of days and I'm sure to cheer up with the kids around.
Posted by md on October 30, 2007 at 10:21 PM MDT #
Posted by Lars Fischer on October 30, 2007 at 11:01 PM MDT #
Posted by Dan on October 30, 2007 at 11:22 PM MDT #
Heh...same problem here...Did the same as you...what a PITA. It took me days to get Leopard running. I SuperDuper'd my drive and tried to upgrade. Yep...BSOD...on my MacPro *and* my laptop. Clearly something isnt compatible. But I did a wipe and install, and copied from my backup with the upgrade and that seemed to work.
In my total opinion, I certainly would have waited. As much as I like some of the Leopard enhancements, I lost a lot of application compatibility that has no Leopard support, such as issues with VOIP clients:
http://support.counterpath.net/viewtopic.php?t=11490
Seeing how I am going to speak at the Irish Java Conference next week...having this incompatibility really sucks.
Other key pieces of software that I use, such as Cocktail...no longer works:
http://www.macfixit.com/article.php?story=20071030122926454
This all makes me wonder if either the companies that make the software don't care and waited to the last second, or if Apple pulled an "Apple" and f'd everyone up at the last moment.
For crying out loud...even Adobe Acrobat has issues!:
http://www.macworld.com/news/2007/10/26/adobelopard/index.php
I'd love to know why all this had to happen when all this got released at the end when all these companies had an opportunity to see what happened before release (read: Apple Developer).
In all honesty...had I known this was all going to happen I probably would have waited a couple of months before upgrading :-(
Posted by Jeff Genender on October 31, 2007 at 02:44 AM MDT #
Posted by Erik Weibust on October 31, 2007 at 08:23 PM MDT #
Posted by Gregg Obst on October 31, 2007 at 10:53 PM MDT #
Gregg - I think the worst parts of Java development are 1) slow deployments and 2) lack of testing the web tier. Rails solves those, but so does Grails. Grails seems a lot closer to home and I wouldn't have to learn a bunch of new stuff - especially since I already know almost all of the underlying technologies. Regardless of whose better, I think they're both great frameworks.
Posted by Matt Raible on November 01, 2007 at 03:45 AM MDT #
Posted by 71.75.158.20 on November 04, 2007 at 03:26 AM MST #
Posted by Franky on November 22, 2007 at 07:53 AM MST #