Also, Apple's not "moving away from Carbon". They simply can't, since I don't see, say, Adobe/MS/Macromedia move on to Cocoa. Sure, it might happen _some_ day, but this hasn't got anything to do with how Classic support evolves, either.
I guess Apple's plan with Classic is this:
1.) Remove Classic from retail versions of Mac OS X.
This has now been done with Tiger. You either already _have_ Classic, because it came with your computer, or you just forget about it when clean-installing Tiger. Most users (probably more than 90%), do not need Classic anymore.
2.) Remove Classic support altogether.
This probably _will_ happen sometime in the future. Whether it'll be in 10.5, 10.6 or finally in 11.0, who knows. But really: Who _cares_? There still will be a few solutions at that point in time (which might be as much as 10 years away!):
- Keep using the last known version of OS X to support Classic.
- Keep a separate machine for Classic applications running on the last known version of OS X to support Classic.
- Replace those freaking old tools, apps and games by alternatives. Most of us have already done this in the days of Jaguar. Many of us have done this in Puma, when MS and Adobe finally got around to release new versions. And some of us even tried to get rid of Classic _before_ that. Me, personally, I have started hand-coding my webpages back in Mac OS X 10.0.x, because GoLive was so slow via Classic that I was actually faster doing it by hand.