I respectfully disagree. Leopard brings us Objective-C 2.0, garbage collection, 64-bit APIs/frameworks, ...
It'd be nice if the garbage collector is already as usable as Java's, after all it's the first revision. And the question remains, if users can expect their developers to code better applications using it.
64 bit is nice if you need it. How many applications can you list, that could
definitely take advantage of 64 bit on a desktop?
... a major refurb of Xcode, a complete rewrite of Interface Builder, Xray, DTrace, Dashcode, the scripting bridge, PyObjC, RubyCocoa, and RoR. It's damn near developer heaven right out of the box...
I can work with Ruby (on Rails) and Python on Tiger already. It's nice that Apple is finally jumping on the train and makes this available in XCode and bridging to ObjC is possible. Sun's DTrace is also nice, but it's not that most of this wouldn't already have existed long before Leopard.
I would make me
MUCH happier if Apple finally would get their act together delivering proper Java support, instead of adding candy. The release schedule is lagging years behind the rest of the world and intransparent. After all Java 6 is really great on all platforms for quite some time, except OS-X. If Leopard can deliver Java 6, I hope it's going to be better than the first 1.5 release in Tiger. I'm afraid that Ruby and Python support wont be much better. So sorry if I don't jump on every feature train you offer yelling "yeah!". Proper long term maintenance of these platforms is much more important to me than bleeding edge features. It's on Apple's side to prove this. There is no established track record regarding anything else than ObjC.
I agree that neither Microsoft nor Adobe will make much use of this API, but I disagree that it's only for amateurs. I think many OS X developers, myself included, will find Core Animation useful for adding richness and polish to their interfaces. With your logic, one could just as easily discount the entire Cocoa API as unprofessional because Microsoft and Adobe products are largely Carbon.
That was no "logic" but an example. Tell me one "bigger" application suite besides Apples own that could benefit from Core Animation. I'd agree though that there will be much room for creativity at a smaller scale for multimedia and presentation application developers. I thought that the next Microsoft Office is going to be Cocoa btw..?
In any case, 64-bit computing is on the horizon and I'm pleased Apple is bringing 64-bit capabilities to Leopard. The arguments against this move are the same ones I saw when the industry went from 8 to 16-bits and again from 16 to 32-bits. (Yes, I've been around that long! 😱)
Now I respectfully disagree. When going from 8 to 16 everything was still in early stages and both ranges rather clumsy, but 16 to 32 was a revololution the day it was available for everybody. At least on the PC platform. Totally uncomparable to 32/64. The 16-bit memory limit was a total mess - everybody cried for more and multimedia was on the horizon (remember 8-bit sound cards?).
We went from text to images. From there to animated images with sound. From there to 3D stills and later animations. We can't go 4D now. You can cut a cinematic resolution movie today on your Mac. I don't think that we will expand our possibilities at the known pace (I thouht different back then). There's still going to be exponential growth of resource hunger at the data center level, where 64-bit is gorgeous, but not on the desktop. We may see a boost again in 4 years or so when data mining possibilites far beyond spotlight become usable for end users.
There are islands today already. HDR image processing, for example. If you take 16 bit of information per color channel, 32-bit hits its boundaries. So Aperture might really take tremedous advantage of 64 bit some day, also Photoshop if HDR editing ever becomes standard. But displays have years to go there. They can't even display complete 8-bit data today.
So long speech, short sense (German saying): 64 is the way to go for the future, but in 2007's and 2008's improvements just because of this are going to be sparse.