I'm becoming less and less enamoured with Stacks the more I use them.
If they were available on the desktop for use as temporary storage locations for current work, I'd possibly find them handy. But in the cramped dock, they're not particularly useful. That they've removed one-click shortcuts to open a folder in Finder is also a bit of a kick in the knackers, not to mention losing the drill-down context-menu. Mind you, I'm not going to miss that quite so much now that the Finder is as fast as a rocket-propelled whippet.
Overall, the Dock's lost a few coolness points for me, Stacks haven't earnt any, but Finder gets several gazillion for working so damn well. I love how network browsing and connecting are implemented - especially with screen-sharing right in there too.
Address Book gets a minus-several-billion coolness penalty due to its loss of Bluetooth phone integration. However, the new Address Book app bundle does contain some Bluetooth icons and the AB prefs file contains a couple of bluetooth references, so perhaps all is not lost for future point-releases.
I'm pretty happy with Leopard other than the faults I've outlined above. It's certainly a solid release. I'm mostly looking forward to what those wonderful 3rd-party developers do with the new APIs. That's one of the best things about the Mac developer community. It's usually pretty short-order between Apple giving them new and better toys to play with, and us getting some great apps that use them!
gkroeger said:
2. No Carbon 64-bit APIs. It's all well and good to push Cocoa and Obj-C, but if cross-platform developers drop the Mac it will hurt Apple. If Adobe and MS leave, you can kiss the Mac goodbye.
True. But the 32-bit Carbon APIs won't disappear any time soon. I think it's been pretty clear since Tiger's launch that Apple's intention has been to gradually re-implement Carbon routines in Cocoa, in a manner consistent with Cocoa's design and approach. If Adobe and MS want to grow the capabilities of their apps along with the capabilities of OS X, they're going to have to bite this particular bullet anyway. At least they're both now rid of CodeWarrior, having moved to Xcode for Universal Binary support. Apple's extension of Cocoa to cover what Carbon does is going to be a gradual thing, hopefully gradual enough that Carbon-heavy developers can move with them at a similar pace.