Confirmed: Mountain Lion sends some 64-bit Macs gently into that good night
arstechnica.com
arstechnica.com
It is still possible to boot the 64 bit kernel and install ML by using a non-Apple bootloader (eg Chameleon), basically turning your Mac Pro into a 100% Apple hackintosh.
It just makes it all the more confusing and misplaced, so I'm guessing the one person that doesn't get it was the author...
Correction: most native English speakers :). I for one didn't.
Do not go gentle into that good night,
Old age should burn and rave at close of day;
Rage, rage against the dying of the light.
Though wise men at their end know dark is right,
Because their words had forked no lightning they
Do not go gentle into that good night.
Good men, the last wave by, crying how bright
Their frail deeds might have danced in a green bay,
Rage, rage against the dying of the light.
Wild men who caught and sang the sun in flight,
And learn, too late, they grieved it on its way,
Do not go gentle into that good night.
Grave men, near death, who see with blinding sight
Blind eyes could blaze like meteors and be gay,
Rage, rage against the dying of the light.
And you, my father, there on the sad height,
Curse, bless, me now with your fierce tears, I pray.
Do not go gentle into that good night.
Rage, rage against the dying of the light.
http://www.poetryfoundation.org/poem/175907Edit: woops, late to the party. That's what I get for leaving a page up for 20 minutes before commenting...
I kid, but it's interesting to see a few warts in the Apple ecosystem. Nobody can argue that they don't make awesome products, but as they slip into the "mainstream" we're going to see that it's more and more difficult to maintain a flawless complexion.
First, they remove the "can't get a virus!" ad, now this, within weeks. Being unable to upgrade your OS is no minor quibble. "It just works" indeed.
Honest questions. As people in this thread with more knowledge than myself have stated, there's a tradeoff in introducing new technology and maintaining legacy hardware support. OS fragmentation seems natural. And the better our tech gets (longer life of devices), the worse the problem will get. Considering how fast phone technology works, why is/was Android fragmentation such an issue?
Optimus L3 was released earlier this year, ships with 2.3 with no foreseeable upgrade path (thanks to its low price). The software is outdated the moment it was released.
I'm looking for Android phone today and still undecided of what to get (inclined to get HTC One X) because I'm unsure whether it will get a 4.1 update or not.
But the fact that there is still an Android with 2.2 available, brand new is what gives Android it's market advantage: cheap phones. For all people who aren't really techies, Android 2.2 does everything you need, and far more than my original Motorola RAZR. That's bad for Android?
Hiring some maintenance programmers to take care of 10.6 or 10.7 security for X more years (and announcing that EOL date!) sounds pretty harmless. How would that hold Apple back at all? They have mountains of cash in the bank and those programmers wouldn't get into the way of 10.8 or 10.9 at all.
You can't just add programmers to mate cutting edge OS kernel features (ie leveraging recent videocards) with old hardware. None of us can speak authoritatively on the case in point, but it seems painfully optimistic to think you can pull this off without introducing a lot of complexity. And then, what happens if the 10.8 team tweaks the kernel during a point update? Yep, better double or triple the testing team.
"Oh, it looks like it'll take some work to get 10.8 working with all of our old AMD chipsets - either we delay release until fall (after Windows 8, unfortunately) or we put some of our "A" engineers on it."
Complexity is the keyword. Complexity and mediocrity go hand in hand. Backward compatibility is a noble goal in many ways, but every generation back of software/hardware you try to maintain exponentially increases the complexity you deal with instead of putting a better new product in user's hands.
HN completely ignores the class of computer users who only need Safari, Mail and some variation of Word, and then live in these apps for years without any major upgrade. In my experience, these people don't even feel entitled to any upgrade and they don't add any complexity to any testing matrix. All they need are baseline security updates, and existing services better don't stop without a plausible reason (see MobileMe). I'm not thinking of MegaCorp here, but rather my own and friends' close relatives.
The machine that got excluded from 10.8 after only 4 years was not a rev-A MacBook Air in the hands of some early adopters but a Mac Mini, the most traditional Mac money can buy. That really leaves little hope that all my "slow adopter" relatives will ever leave the Windowsverse.
I work with people who work with lab software which is happily running OS X 10.2 Jaguar. It's no different than the XP box in the corner, as long as everyone understands that the checkbook has to come out when it breaks.
On the other hand, the quarter million dollar cytometer is going to be running Windows NT 4 Embedded, and when that ATA-66 hard drive fails or the software becomes unable to talk properly with the modern world anymore, it's on the vendor to make it work again. The support typically blows, but it's their problem to handle and none of them are going to be relying on Apple's memory-hole platform.
As long as Lion gets security updates (2 years, minimum), there's absolutely no need for an upgrade. After that, you can just disconnect it from the Internet and use an stronger password.
I completely agree and that's a very valid scenario. Apple tactical advantage is that consumers have completely different usage patterns and expectations than the enterprise/lab (which Apple essentially ignores). If %95 of consumers either (a) upgrade within five years or (b) are completely perplexed by the notion of updating their operating system at all, then Apple are at a huge efficiency advantage EOL-ing technologies around the five year mark. As opposed to having top engineers work on maintaining compatibility with deprecated APIs, old hardware, etc. for 15 year old software.
I've been running a machine with 10.5.4 on it for 3 years, and just 2 days ago got a brand new Air with 10.7.x
I notice some differences, sure, but nothing that makes my old laptop "obsolete" or "EOL" compared to the new one. The real difference is the new machine has twelve times more storage, 4 times more RAM and another CPU core.
It is still my primary machine (well, I've got two of them actually).
Hell I tried to downgrade to SL, but that's not possible due to drivers.
Lesson learned. Also,I'm STILL being forced to download the OS from the App Store. I wouldn't mind that so much if the Store didn't have performance issues.
Also, I never had any problems downloading Lion or Mountain Lion from the App Store. The downloads were always fast (I am on a 120 MBit downstream connection).
One would expect that they also release it on a USB stick as before (or DIY).
Although, I can't place the blame entirely on Apple. I find that for any consolidated release OS, a reformat is ALWAYS the way to go (after waiting a good long time for all the bugs to be ironed out). Hopefully one day Apple will drive the cost of their software down so much that they'll just go to rolling release.
I have updated 3 personal Macs to Lion. Some upgraded, some a clean install. Didnt have a problem with any of them.
What broke for you? Drivers for exotic hardware? (on that front, I use Wacom tablets, Midi controllers and external FW audio cards and had no probems with either in Lion).
On the other hand I refuse to install ANY haxie.
Seriously want to know what broke for you -- and I dont mean stuff like "I prefered old Expose better"....
- silent DVD-ROM read errors causing perma-botched upgrades, even though everything should be CRCed and nothing throws any errors at any point along the way
- pathologically long install stall-outs (40 minutes+)
- pathologically slow performance at first restart, usually on older RAM-constrained machines trying to re-thumbnail everything
- Significant keychain issues requiring creation of an entirely new keychain
- Spotlight issues requiring a first or second re-index
- Mail.app upgrades are quite problematic, especially when moving to V2 layout or accessing previously configured accounts
- Now-missing JVMs causing significant problems during first boot
- Lion download progress bars blowing some internal math and going for that 235905329052 gigabyte
The biggest hassle I think is exploding third-party software at first logon. Things like garbage rinter+scanner managers freaking out because drivers got moved around underneath them cause a flurry of popups that frustrate techs and freak out novices.
Silent DVD errors, install stalls, keychain and Mail accounts missing sound like genuine bugs.
As for the rest,
>- pathologically slow performance at first restart, usually on older RAM-constrained machines trying to re-thumbnail everything
This doesn't sound like an OS bug, more like something to be expected.
>- Now-missing JVMs causing significant problems during first boot
Sure, but what uses Java at boot?
The above and third party printer/scanner managers freaking out, sound like totally orthogonal issues to OS bugginess.
If anything, I would _expect_ to have to install new third party drivers with an major OS update.
I don’t see any roadblocks to installing it. It already works much better than Lion.
Apple has always pushed for letting go of the past in order to reach for the future. I mean, come-on, the original Apple Macs had no arrow keys...
That said, I have an HTC Titan and don't really care.
[edit for typos]
If you don't have Lion, I think you can still get that info from the window that comes up when you click "More Info…", but I forget where (and don't have a machine running Snow Leopard handy ATM).
EDIT: The required models are listed by Apple (linked in the article): http://www.apple.com/osx/how-to-upgrade/
iMac:~ Flow$ ioreg -l -p IODeviceTree | grep firmware-abi
| | "firmware-abi" = <"EFI64">
iMac:~ Flow$
EFI64 means ok for ML. % ioreg -l -p IODeviceTree | grep firmware-abi
| | "firmware-abi" = <"EFI32">
on an old (white polycarbonate) iMac.