Comment Missed opportunity (Score 1) 117
"..., says WHO"
"..., says WHO"
Sure, it’s perfectly technically possible to create an end-to-end encrypted chat service. But you’re a fool if you think Twitter and co. are doing any of that implicitly, when their entire shtick is public message exchange. And even DMs are just "Direct", nobody said anything about Private.
If anyone thinks any communication on Twitter or Facebook or anything like it is private in this sense, they need to reevaluate their head.
Is the data on their servers? Do they have access to their own servers? Ergo, they have Trump's toots and could hand them over.
I'm shocked, SHOCKED, that anybody is shocked about this.
Oh, you mean the ones with the Eternal Battery(TM)(R)(C) from Acme Corp. Well then, nobody's keeping you from buying one of those instead.
[...] With iMiser(TM) disabled, your iPhone may unexpectedly turn off when you receive important phone calls or are trying a take a video of your kids.
FTFY
Indeed, all other phones are always slow, not just after their second or so year. Brilliant tactic.
And all other batteries last forever too, obviously.
I agree that a warning dialog might've prevented some drama here. OTOH, there are a ton of issues associated with any sort of warning dialog too, and such a thing may in fact create drama on a regular basis. Support costs would increase with more people walking in with phones showing "some weird error message". Or the error message would be ignored, as most error messages are, and nothing would change. At the scale of iPhones, such things matter. There is no easy silver bullet.
Apple tries to make its products as free of error popups as possible and "just have them work"; unfortunately they fell on the wrong side this time.
If the media wants to find a 'gate, they'll find a 'gate. There's nothing Apple coulda done to prevent it besides BEING PERFECT IN ALL REGARDS AND CREATE PERFECT EVERLASTING PRODUCTS.
a) Not dunnit in the first place (device slowdown as battery degrades). That was a crappy thing to do and serves to highlight the "mandatory 18 month upgrade" that's so much a part of the Apple business model.
You'd really prefer the random crashes instead of the degraded performance, ya?
Do you request the same thing of executives at CPU manufactures who decided to throttle your CPU when it's about to overheat?
*crashing phones or no crashing phones, FTFY.
The previous version of the OS won't boot from APFS. So instead of being able to surgically excise enough of the OS to let you reinstall the previous OS (IIRC, this minimally amounts to turning off system integrity protection, booting from an external drive or recovery partition, and 'rm'ing a handful of files, but I usually nuke all of
Having a full backup (Time Machine) has always been the only supported and recommended option to begin with. If you even know what dd and rm is, you're so far advanced beyond the typical user that you're entirely on your own and that you can find ways to downgrade if you absolutely have to. Downgrading is a rare occurrence in the first place, and it's even rarer for someone to attempt it the way you do. This is not a realistic concern for enough people to worry about.
And how is this any different from software breaking for any other reason? Would the same TFA be posted with "Deprecation of library Foobar not optional"? That's one common reason why something breaks after a system upgrade. Why make such a big fuss about the file system in particular, which is probably one of the least intrusive changes since it works at an opaque level to most application code?
Your point being? Do you believe a FAT32 USB stick will silently be converted to APFS when you plug it into a Mac? Errrrrrrr... no.
"If you want to know what happens to you when you die, go look at some dead stuff." -- Dave Enyeart
