Your argument doesn't explain why PC desktop sales are also sagging badly, since they don't have the same reliance on all-in-ones, etc.
If anything, Apple is in the leading edge of ongoing trends in customer preferences.
Such a delicate flower.
Out of five Mighty Mouses, three of them purchased shortly after they were introduced, we've had 0 hardware failures. They're ergonomically fine (I'm a technical writer and spend a lot of time using them).
If the scroll bean hangs up, turning the mouse upside down on a fabric surface and sliding it a bit brings it back to normal function.
Another case of YMMV.
Sure thing, Al. Bulletproof windows and shatterproof glasses are always made from "cheap plastic".
To answer the poster that you snarked:
Unibody just means that the main body is one piece, without a separate openable battery compartment.
The new long-run battery is larger than previous replaceable batteries, and does away with the battery bay of previous MacBooks. Tends to be stiffer, without adding weight, too.
Suck it up, Ace.No, it will only run when you're running PPC code, which the printer driver seems to be. Otherwise, Rosetta has no perceptible effect.Even the printer makers will take time to update their ancient, creaking print drivers.
It's not like they couldn't see that PPC support would be going away, and not in some dim misty far future.
And hope that the page location URL never, ever changes in the future.
Unless you know what Apple's internal testing/build schedules were, and the cutoff dates for releases, you can't say this with any certainty.
There are only so many resources available to any real-world entity.
Maybe Apple should just add a script that pops up a message on installation saying to go over to Adobe and get their flipping flashplayer plugin yourself.
That would go over well.
Sigh.Here's how software releases work: You define a set of resources (applications, etc.) that will go into the package. You specifiy a schedule for release, testing, etc. It will change, depending. Part of that schedule includes cutoff dates for submissions. Because testing takes some time; you do not want to drop in the latest shiny thingie at the last possible instant before you send the package off for duplication. Well, not if you want to stay in business....
Bite your tongue, man!
You want it to act like the auto-update "feature" with other Adobe products? The feature that can't find the application, bails after spending who knows how much time futzing around, then tries to do it again the next time you use the application.
A major software release like Snow Leopard contains thousands of pieces of software, it's hard to catch everything all the time.
It could depend on when the package structure was put together, which would usually drive the versions of third-party content included.
On top of that, if you're doing your job right, you can't just replace one of those items, or shouldn't, without testing its effect on the product.
Given time constraints, it's probably better to go with what...