Letting us downgrade iOS.
I get it. It means potential security exploits.
But at least let us make the choice wether we’d prefer those to shiny new, and different issues that seem to be growing in number.
Fine, I’ll wait for the jailbreak and collect the goddamn SHSH blobs or whatever, if that’s how far you’ll make me go.
My, how lucky you are that GarageBand iOS has no peers (namely its integration with Logic), or I’d downgrade to a dumb phone and start carrying a palm pilot again.
Security patches need to be entirely separate to performance degradation patches. You should be able to say no thankyou to your vendor gimping your product without them holding the "no security for you" gun to your head.
When you buy a device, security patches for that OS for 5 years should be a requirement for the device being fit for purpose.
For anyone not aware, Apple is extremely hostile to device longevity and 3rd party repair . They have had issues with hinge design in MacBooks as well as the Bendgate crisis for the iPhone 6 series.
They bricked phones when people had other repair shops fix their home buttons (Touch ID sensors).
Apple wants to control everything, sell you a device with a short lifespan, and then force upgrades.
1 - https://m.youtube.com/watch?v=26cNHSilikI
usual caveats apply, make sure that mobileconfig is really the mobileconfig you're looking for.
And now i can’t even modify text properly because the drag n drop interfeers with cursor positionning.
Now there's no JailBreak for iOS 10.3.1 32 Bit devices, and the OS lags like never before. Really miss iOS 6...
A hammer analogy?
If it ain't broke don't "fix" it.
Car analogies only please.
(Ironically "if it ain't broke..." doesn't apply to Apple)
In addition,I like my hammer comment for exactly the response you gave. It triggers an almost visceral response in people who are tech literate. Call it subtle trolling if you will, but it's trolling designed to make someone think.
Also, I'm not always a fan of "if it ain't broke don't fix it" it has it's place though. More importantly for me is to have well designed solutions that are easily maintained that work. "Iiabdfi" usually only applies to duct tape systems and it surely is a principle to remember when encountering them.
I'll probably never update my phone to a new major iOS version until it's been out at least 6 months. If iOS11 is ever reaches the point where it's as good as iOS10 was, I'll install the tvOS beta config and prevent updates. At least until I'm able to take the time and research if the latest version of iOS12 is in good shape for most users.
An even better idea, and what I'm probably going to do, is to only update from and to the last version of each major iOS. Then you don't have to time anything at all and do any research/guesswork. Your device just works as well as it can, for the longest period of time. Everyone else beta tests Apple's software for you.
I really wish I were on 10.3.3 and had the tvOS profile right now. Never again.
Want to upgrade my old phone to take advantage of GB's Logic integration, but I can't decide whether to get an iPhone 8 Plus or the standard model... Does screen size make a big difference on that app? (do you know...) Thanks
I am using an SE, because I dislike larger phones (though the 4.7" may still be ok).
That was my point though. People make a big scuttlebutt over these things, but they're quickly forgotten and don't doom a company forever.
I'll put the reaction to Apple's screwups on the same level as the reaction to LG's when I see a class action lawsuit.
Something doesn't have to be good in any objective sense, to be the best. If everything is bad, a very bad thing can still be "the best."
You've to remember people pay premium prices for Apple stuff. If I buy a $300 Moto whatever I'm much less inclined to complain if it breaks vs when I'm buying a $800+ iDevice.
Nah. Look at Samsung: you can make a TV that spies on you, a washing machine that explodes, and a smartphone that spontaneously catches on fire. And then go take a look at how their stock is doing this year.
We've reached the pavlovian phase of western consumer culture: we'll just keep on buying and buying and buying, no matter what.
Americans started buying Japanese cars because so many of them had direct poor experiences with American quality in the 70's to 90's.
I don't think that has necessarily happened with Samsung, yet.
they did get a lot of bad PR for that and it was running joke in the tech industry and it still is even though they have recalled the faulty devices.
A bootloop due to a date value is just sloppy.
...which came as a result of sloppy quality control...
It's not a matter of one department, it's a matter of culture which starts from the top. Jobs insisted on perfection, and that permeated the entire organisation. Cook is satisfied with gimmicks and is contented to just coast on the reputation Jobs earned. He just doesn't have the personal stake Jobs had, he's a manager not a leader. Just like the iconic HP was never the same once Fiorina took over.
> "Just like the iconic HP was never the same once Fiorina took over."
HP was in trouble well before she joined the company.
She is getting more flak than the other terrible CEOs, but IMO it isn't caused by the fact that she's a woman. At least not directly.
Back when she was appointed as a CEO, media were treating her like a second coming of Jesus (which probably indeed was caused by her gender, she was a perfect role model for feminists). That set expectations bar really high, and when she failed to deliver, people turned against her.
 - https://en.wikipedia.org/wiki/List_of_mergers_and_acquisitio...!
 - https://www.theguardian.com/technology/2013/feb/25/yahoo-chi...
 - https://www.recode.net/2016/2/2/11587472/marissa-mayers-big-...
 - http://www.businessinsider.com/yahoo-ceo-marissa-mayer-blows...
It seems like a house of cards right now, and it will only get worse as they keep having the next crunch time just to deliver on an arbitrary management deadline...
It’s been that way since the 1960s.
It “has to be done” sometimes, but put that day off as long as possible.
Considering that some people will continuously adjust their iPad clocks into the future to be able to play Candy Crush without waiting (sic!!!), this bug must have affected people, and was certainly somewhere on Apple's radar.
It's just that management then shrugs and sticks to yearly releases instead of working down this mountain of debt.
Its only a matter of time until every silicon valley tech company faces the same problem.
I work for a Bay Area technology company with a decidedly mediocre engineering team.
My experience over the past 2-3 years is that the worst software engineers (at our mediocre organization) are being hired by Apple. This is totally anecdotal and the sample size is maybe five. But I just cannot escape the fact that Apple continues to hire our engineers that barely know how to program.
Hiring engineers in the Bay Area is hard. I'm sure Apple has a deep bench of talented engineers, but my own anecdotal experience tells me they have very much reduced their standards.
- Everything must be Scrum or a similar sprint system: https://news.ycombinator.com/item?id=8836734
- Move to an open office layout to foster collaboration: https://news.ycombinator.com/item?id=14962663
- Kick out high-performing "heroes" like Scott Forstall
- Instead, build teams of mediocre (but probably nicer) engineers. They can then lift each other up through positivity and pair programming.
This is of course a lot of speculation (and wishful thinking) on my part, and honestly it's likely that any process would be doomed to failure under Apple's self-imposed deadlines. But I almost want to get a job at Apple only to see what it's like on the inside.
In the last years their scope has expanded immensely, both hardware-wise (iPhone, iPad, Apple Watch, Apple TV, now HomePod) and software-wise: AirPlay, CarPlay, Homekit, HealthKit, AR, Apple Music, Force Touch, machine learning, Siri, Handoff, Airdrop, Emoji with face recognition, etc. A lot of these technologies work somewhat, but are glitchy.
Of course, there are many times larger than the Apple of 2007, but managing an extremely broad palette of technologies is difficult. Especially when you want them all to produce something in-sync in the autumn. In some sense, Apple may have spread themselves to thinly.
I think think that we would be better served by an Apple that was more focused on core technologies and would let the third-party ecosystem focus on applications. Or perhaps completely separate divisions that would focus on macOS, iOS, and hardware. Or shipping features when they are done (rolling-release style) rather than one big drop every year.
At any rate, their current direction is hurting core, traditional use cases for Apple products. E.g. Preview.app/PDFKit has been really terrible the last two releases, to the point where I can barely use it for previewing my lecture slides, etc. Basic technologies like PDF rendering used to be stuff that they had nailed down extremely well.
> let the third-party ecosystem focus on applications
I'm worried that this is exactly what Apple tried to do with tvOS, and since it hasn't worked out (Amazon is still MIA), they're now going to spread themselves even thinner by producing content and related apps themselves.
I have yet to find a pdf viewer which does anti-aliasing right except acrobat reader. If you have two colored objects with a common edge on a white background, that edge will be lighter in color.
WHY that happens is much less clear to me.
Things have been getting worse for quite a while. It appears to have finally hit a tipping point.
iPhone 5S to X (plus iPads, Apple Watches, and the iPod Touch) is a lot. All with different aspect ratios.
Jsx and the rendering model of react is 10x better than constraints in code or storyboards.
Getting android nearly for free is just a cherry on top.
Right, and the faster development cycle with hot or manual reloading makes it really easy to be productive.
I just need to figure out a few integration issues like navigation within our native app and localization using our current native scripts, but all the newness and uncertainty is really exciting.
Sorry I just realized my previous message autocorrected to nonsense.
Oh and some of you may remember the time that non-recurring alarms just stopped working one day on all iOS devices.
I still have an iPhone for reasons. But damn, I’d like to have one version of iOS that doesn’t have quite so many bugs.
I love Apple but Tim has got to tighten that ship.
I guess we are supposed to.
Apple still won't let us change the default browser from Safari to Chrome/Firefox for links clicked in Mail or iMessage. Its very annoying.
Perhaps I have an overdeveloped sense of entitlement (genuinely: there is no irony or sarcasm intended here), but one reason I pay for a premium object, device or experience is to avoid hassle and friction, so it's pretty frustrating when that's exactly what I get.
It’s the whole fucking reason I started paying extra for Apple products to begin with. If I were willing to put up with this kind of sloppiness, I have a variety of options for less money.
Recently, the quality has gone done. The software has more bugs. Apple apologists say wait until .2 or .3 and it'll improve. This takes 4-8 months. So, people are supposed to "enjoy" a crappy experience on their new iDevice for 8 months and then it gets better? I simply don't understand how anyone could argue this.