4 ms·
It saddens me to say this, but it seems that in the software engineering department at least, Apple is stuck creating a lot of deckware. What I mean by this is
by disgruntleddev 4y ago
It saddens me to say this, but it seems that in the software engineering department at least, Apple is stuck creating a lot of deckware. What I mean by this is that there seems to be a cultural environment in creating new products that look great at a keynote launch, but then post launch are abandoned.
Many bugs remain indefinitely post-launch. Many features seem to languish to become replaced with something nearly identical and also not finished. Often you'll hear the advice to 'file a Radar (Feedback)', but among developers for Apple platforms it's become a running joke. It seems just to disappear into the aether without comment or resolution. The internal teams have moved on to the next launch.
It's tiring year after year to see polished marketing videos tell you 'what's now possible' but for it to be so unusable due to a myriad of bugs. And worse is the lack of acknowledgment – please don't send developers down a dead end if you know API isn't production ready. Let them know, communicate where it falls short – we can handle it.
At the end of the day, I just wish they'd slow down and polish what is already there.
- Dalewyn 4y ago>Many bugs remain indefinitely post-launch. Many features seem to languish to become replaced with something nearly identical and also not finished. Often you'll hear the advice to 'file a Radar (Feedback)', but among developers for Apple platforms it's become a running joke. It seems just to disappear into the aether without comment or resolution. The internal teams have moved on to the next launch. First time? :V This isn't an Apple-specific problem.
- disgruntleddev 4y agoYes, that's exactly the attitude I'm referring to. Apple used to hold themselves to a higher standard.