"Some well-informed poster might come up with the magic bullet."
Linux
Well someone was bound to say it.
There are scattered reports of problems with Apple's Snow Leopard update that was released yesterday. Ah, tradition. Over on the Apple Discussions forum, early updaters are reporting a series of troubles after upgrading to Mac OS X version 10.6.4: Complete installation failure. iTunes running on an iMac caused the UI to …
Every time El Reg report problems on software release from any manufacturer (whether it be Microsoft, Apple, Google, or anyone else), a bunch of people come on the forum and say, works for me. You do realise that these are the most useless posts ever? No big software company is going to release software that fails to work in testing. Unfortunately, the number of live configurations means that it is very hard to test on every hardware/installed software combination. Even if failures happen on less than 1% of cases, it is a huge issue for people it fails on. Also, in many cases, people with multiple machines to upgrade often have similar software and configurations on all machines so quite often failures are clustered.
Remember the Toyota recalls? The vast majority of people's cars had no problem at all. But a tiny percentage had problems with stuck accelerators, and it became an international incident. With OS upgrades, if 0.01% of people have an issue, that is still lots of people with an issue.
All I ask for is a basic understanding of statistics. With your sample size of 2, your ability to predict that no-one else has a problem is virtually non-existent. If you think Steve Jobs is a saint (or Ballmer/Gates or anyone else), fine. But please don't belittle genuine problems that users have just because your 1 or 2 cases went fine.
Idiot!
....but, as the ranter above said, the default position is that it will work. And it WILL work for 99.several nines% of updaters.
But those that fail are the interesting ones - especially if yours has also failed. They can be grouped together and solutions found.
I agree - "Well, mine worked OK" is about as futile a post as you can make on here when discussing updates. Won't stop them happening, though.
ok i'm an idiot, but you must admit you don't understand statistics AT ALL.
how do you calculate the 1% you mention without counting all data points? if you want to do statistics you have to count 99 positives and 1 negative to come up with the figure. don't you? if people only posted 'it failed', 'it doesn't work', etc how would you know it's 1%? in that case STATISTICALLY it's a 100% failure.
So. Join the club, idiot #2.
:)
Actually, it is clear you don't understand anything - not just statistics.
People generally don't report success - at least not by calling helplines or posting in help forums, so you judge success by the absence of complaint. Therefore, percentage failure is the number of reported failures divided by number of sales. Simple. People in every industry in the world follow this, unless they are selling so cheap a product that people will not complain if it goes wrong.
Muppet.
I must apologise. You must be a very wise man indeed. How stupid of me not to understand the obvious.
PS. Sorry, I must be really stupid, but what's your name? You have signed both posts differently. The first one is signed by 'Idiot' and the second is signed by 'Muppet', so who of those two are you?
Yes, you're right about statistics, but what you didn't do is apply them to the article to begin with. Talking about blowing the problems out of proportion, El Reg, has done a fine job of turning a mole hill into a mountain (or choose any other better analogy). Trawling through support forums is about the least representative way to sample something, but a great way to whip people into a frenzy enough to read the article and get some adverts from it.
This article, and a few of the posters here, are essentially suggesting that this update is borked because it affects <= 0.01%, let's say, of users. I'm sorry, but based on what you said, it's just not worth reporting. Much like a similar proportional volume of problems for Windows update often goes unreported. This is link-bait from a publication that has a growing unhealthy obsessed with Apple, and Jobs in particular.
And some people wonder why the iPhone is locked against just any old app being installed. What is happening for a few with MacOS 10.6.4 update is exactly what Apple wishes to avoid with the iPhone. Still, it happens with the iPhone but not as bad.
As for myself, never had a systemic MacOS update problem. Sometimes badly written apps would not run correctly, but the OS always behaved. Running MacOS since 6.0.2.
> And some people wonder why the iPhone is locked against just any old app being installed.
Yes. Because locking down your device is the answer to bad vendor supplied software updates.
No. This situation points to quite the opposite conclusion. End users should be the ones in control. They should be aware enough to decide to "just say no" to bad vendor updates or bad software in general.
The nanny is a junkie.
> And some people wonder why the iPhone is locked against just any old app being installed.
"Yes. Because locking down your device is the answer to bad vendor supplied software updates.
No. This situation points to quite the opposite conclusion. End users should be the ones in control. They should be aware enough to decide to "just say no" to bad vendor updates or bad software in general."
Let me get this right. End users should be the ones in control because when they are, they'll install 3rd party add-ins, plugins and patches that prevent the official ones from working properly...?
Better to prevent users with that kind of limited intelligence from having any say over the contents of the system at all!
Yeah the iPhone is locked down because Apple can't write an OS that 3rd party apps can run on... is that really your argument? It’s got nothing to do with the well-documented control that Mr Jobs insists on having over what YOU do with YOUR phone.
Even if that made any sense whatsoever the fact that Apple, with total control over the hardware base (unlike MS and Windows), can’t even update their OS without screwing up some of the major apps in use on their platform is pretty piss poor.
I’m sure all this will amount to ‘features’ that you are willing to pay for.
Twat
"Yeah the iPhone is locked down because Apple can't write an OS that 3rd party apps can run on... is that really your argument? It’s got nothing to do with the well-documented control that Mr Jobs insists on having over what YOU do with YOUR phone."
Jobs has very little say over what I can do with my phone. There is an application for iPhone for everything I need...
"the fact that Apple, with total control over the hardware base (unlike MS and Windows), can’t even update their OS without screwing up some of the major apps in use on their platform is pretty piss poor."
If you'd looked at the posts at the Apple website (linked from the article) or read any of the people who commented here, you'd know that it's a tiny minority of users. (roughly 1 user reported each of the problems ;)
Of course, you could always compare this to the count of people who have experienced problems with MSs OS, updates and applications...
And some people wonder why the iPhone is locked against just any old app being installed. What is happening for a few with MacOS 10.6.4 update is exactly what Apple wishes to avoid with the iPhone.
----------------
This would be a brilliant argument, and defence of Apple's lock-down of the iPhone. Until you remember that the update to iPhone OS 3 went horribly wrong for a significant number of people and caused the batteries to go doolally. Or was it the upgrade to iPhone 2? Oh no, my mistake, I think it was both...
And there were plenty of reports of that update bricking some people's hardware... Particularly bad in the case of version 2, where Apple totally controlled both hardware AND software.
Actually I don't think anyone expects Apple to release a perfect update that won't cause any problems at all - because testing on all configurations is a practical impossibility. There are 2 reasons Apple are taking extra grief for it:
1. The rather arrogant (and hostage to fortune), "It just works" [tm]. Which with the smugly superior 'I'm a Mac' adverts is simply begging for piss-taking.
2. Apple make it really, really, really hard (in fact impossible on the holy iPhone) to revert to a previously working OS configuration. Which control freakery deserves the regular kickings it gets Apple.
3. I know I said two. So I lied... Apple's piss-poor communications. If they'd just talk to people, and make a tiny effort to appear that they were listening, people's frustrations would be reduced immensely and then they'd be more forgiving. Which nicely links back in to point 1 about smugness and arrogance.
"Until you remember that the update to iPhone OS 3 went horribly wrong for a significant number of people and caused the batteries to go doolally. Or was it the upgrade to iPhone 2? Oh no, my mistake, I think it was both..."
Urrm.
It was neither.
There were problems - a very small number but greatly publicised.
I looked at the posts on the forums that El Reg linked to. There are less posts there about some of the problems than there are on this article. There only seemed to be a handful of people who had problems too...
As always, this article is completely worthless without some indication of how many people are having the problem.
And don't try the "there are 50 posts in the thread" argument. If there are 50 posts, 1 is the person who posted the original problem. 27 are people saying "mine works fine". 15 are people saying "Macs suck". 5 are suggestions from people on how to fix it. And 2 are spammers trying to sell you Louis Vitton bags.
Also, it would also be useful to know how many of the people having problems have installed some haxie that does stuff by bypassing the OS and inserting their own code - which almost always leads to problems on upgrades.
Nothing to see here.
I spent a few years at a helpdesk that supported a few hundred OSX machines, aaaand I don't recall any problems that were traced back to updates (which were applied nightly by a cronjob, because our users were, on average, dense enough to panic when an update notification appeared.)
That's not to say that Apple didn't give us a whole heap of extremely random problems, or that I rush to install updates as soon as they're out, but most of the time there was no problem with updates, and when there was, it was /always/ something incredible that had been done by the user.
One memorable example:
Power User: OSX Update broke my firewire
Me: Be right down to take a look
...
Power User: See, all of these 11 firewire devices and 2 firewire hubs don't work any more
Me: Tried plugging and unplugging?
Power User: Yes
Me: Lets try again
PowerMac G5: Starts smoking, flames shoot out the firewire port
Me: Good thing we get the extended warranty
I suspect that one wasn't any sort of software problem : -)
No problems on my upgrade done earlier today on a Mac book pro and iMac. Of course I have not messed around with the machine. Maybe that is the key and why Apple are keen to have upgrades to predictable environments. Similar to most large corporates who have a lock down client and do not all "gifted amateurs" to mess around particularly in Windows....
Absolutely ZERO problems here.
It's inevitable that a small number of people will have a problem. The vast majority of issues are caused by incompatibilities with some third-party application, utility, system extension or hack that hasn't been updated for Mac OS X 10.6.4 yet.
If people weren't so keen to install hacks and other programs that make use of unsupported API's etc. there would be far less issues.
These stories are exactly why I always wait a month before upgrading to the latest update. Apple don't seem to bother beta testing anything these days, then again why should they when they have paying customers willing to do it. I double the waiting time for updating my iPhone due to the retarded practice of not being able to downgrade the OS if there's a problem.
Still the early adopters are good for a laugh.
On my ff 3.6.3 homepage /newsnow.co.uk/ totally appeared in Korean? Some screwed codepage? Lots of boxes and other junk. Resolved by forcing ff to use a working font like lucida and ignore the HTML page fonts request. Only happened on my iMac, I had recently noticed some false font "duplicates" in 10.6.3. I did the 900meg combo update.
(Nexus.froyo fun next week??)
I got this not after apples update... i am sure it was the Office update... now Word hangs so often i am using either Tetedit, Page or NeoOffice. Itunes hangs now often and once then happens.. the system never shuts down but needs to be forced.
Seems also to happen when Vmware is running... this was updated a few weeks ago also. Not Word 2008 + Wmare dont work...
Trying to hold off a re-install as too busy to piss around so simply finding work arounds...
this all reminds me of windows....