From the link: "The important distinction is of intent. In the benign explanation, a slowdown of old phones is not a specific goal, but merely a side effect of optimizing the operating system for newer hardware"
When we try to judge intent we do judge the context. So let's look at the context: people do know that iPhone updates will probably slow their device(even though Apple doesn't tell them that). And there's no way to stop the nagging update notification (aside from jailbreaking).
So let's not be naive. Maybe it's hard to prove at the legal level, but there's a pretty decent chance that this is intentional by Apple.
EDIT: if you upvote, please explain why you think this is wrong.
Software getting slower with updates is a fact of life. It's been an obvious and expected thing since I started being aware of computers and updates in the late 1980s and I'm sure it was a thing even before that. The odds that Apple is doing this on purpose, rather than as a standard side effect of cramming ever more features into their stuff, are so low it doesn't bear more than a moment's consideration.
What's next, people say Apple deliberately destroys batteries after a few years, rather than being a natural consequence of battery chemistry? Apple deliberately makes their screens shatter when dropped?
I'm not arguing against the update making the device slower. But the fact it's built so people would upgrade(via irremovable nagging), even when it's clearly not what's best for them.
Huh? Of course you're not arguing against the update making the device slower. You're arguing that the update not only makes the device slower, but that this is a deliberate action by Apple to make older devices slower. And I'm saying that's ridiculous since it happens to pretty much all software anyway and all Apple would have to do to make this happen is just develop updates the same way everyone else does.
Why? Copy FROM clipboard would be, sure. Copy TO clipboard... OK, I can come up with scenarios where it'd be a problem, but they're pretty far-fetched.
Run a timer overwriting your clipboard every 10ms. Prevent you from copying anything off a webpage and instead replacing it with a copyright notice. Etc., etc., etc.
Flash has offered these same clipboard APIs for years and these clipboard "attacks" have never been a problem before. I don't see how replacing Flash clipboard APIs with HTML clipboard APIs will change web developers' behavior.
I may be a sentimental old fool, but 8088 Domination genuinely brings a tear to my eye. The perfect timing of the "I WAS WRONG" reveal (i.e. "Oh look, this IS graphics mode") and the familiar breakdancer appearing - greatest callback in demo history. I really hope the room erupted into applause at that moment - just perfect.
5 years seems like a long time to wait for a tax refund. Especially tax refunds totalling $2500+ are quite common here in Australia. We have a PAYG system too.
I remember someone (not me, oh no...) used one for NT4 with inadequate policies to get Admin access.
Create a batch file with the content:
net localgroup administrators NewUser /add
...then stick this into the 'StartUp' directory for All Users. Break something. Call support. They log in as Administrator, running your batch file in the process.
NewUser would be created with Admin rights. You wouldn't promote your own login, of course.
> Anyone knows what their software development process is to get that kind of confidence?
If it's NASA confidence, waterfall every time :)
Having worked in that sort of environment (everything about the system has been analysed on paper before a text editor is launched), don't knock it until you've tried it. This wasn't rocket science either, it was export refund batch jobs. In the 21st century.
No. Story linked from daily mail (that's not a "source") is more nuanced.
http://www.nytimes.com/2014/07/27/upshot/hold-the-phone-a-bi...