I’ve never understood Apple’s motivation for sticking to the S path, year after every-other-year. The most positive spin I can put on it is that it feels compelled to tell the “truth” about the phone’s form factor.
Since phone buyers today have distinctly different likes and needs, I have no problem with multiple models. Four models of phones isn’t complexity, it’s simple choice.
If different style iPhones are destined to co-exist, wouldn’t it be nice if the family felt like a family? Wouldn’t it be great if each name indicated the phone’s reason for being, and reassured buyers that it contained Apple’s latest technology?
Previously: Switching to an iPhone SE.
Pen & Paper Software (Hacker News):
But checking every name could get tedious. How about we just look at every prefix-less class name that Apple has used?
If we were to use any of those classes, the compiler and linker would
not complain. But if you used
AppleSpell in a video game to
represent the spell an apple casts on your player, and you override
some important methods like
init to do something relevant to your
own game, you might start seeing very strange behavior!
Apple may roll out updates to frameworks between OS updates, which I believe has happened before. Ultimately the best solution is to test your app regularly and pay attention to your logs.
I wonder why Apple doesn’t have an internal tool to prevent shipping unprefixed classes.
The quick and simple solution if you want silent charging? Swipe left on the lock screen to activate the camera and then plug in the Lighting cable. No chime. No buzz. Then press the Home button to return back to the lock screen.