5 ms·
Concluding that Apple doesn't care about developers has become a vogue statement to make partly because Marco has taken to saying it routinely. It's not totall
by gress 12y ago
Concluding that Apple doesn't care about developers has become a vogue statement to make partly because Marco has taken to saying it routinely.
It's not totally unreasonable to needle at Apple because there are lots of things they could do to improve developer relations, and openness about service status and reliability is clearly one of them.
On the other hand, taking it as true that they are actually indifferent takes a bizarre leap of logic, given how much effort they put into the tooling, the documentation, WWDC itself, making WWDC content available to those who can't attend, etc.
It's obvious that they are overloaded and are having problems scaling support for their developer community. It's far from obvious that they are indifferent.
[edit: downvotes - of course, because I'm not vehemently attacking Apple. Bear in mind that I don't think it's bad to needle at Apple, but I think it's only because people know that Apple does care about what developers think that it's worthwhile. Meanwhile let's not get things out of perspective.]
- Spearchucker 12y agoHow do you think they stack up against Microsoft's support for developers?
- mahyarm 12y agoIt feels indifferent because talking to apple is like talking to a wall. You never get a real response, ever. And if you do, it can be the height of laziness. All of those things also benefit apple internally for their own development work.
- debian69 12y agoSee my experience is entirely different , the 3 bug reports I've filled got replied to eventually and dealt with in OS updates. There is an argument for catching a server down response and alerting the user that the third party server is down. But end of the day apple do suck when it comes to getting a fast reply , as a enterprise customer of Apple we often feel like its worthless talking to our reps. Since outside the US no apple rep has any pull in any way.
- gress 12y agoI don't deny that it feels bad. I have filed radars and had them trivially closed or marked as duplicates. However, you are flat out wrong to say it's "Lazy", because that implies that they have the time and resources to devote to a more thorough handling of these cases. I'd prefer that they spend more time fixing bugs and improving the software than handholding developers. Now this doesn't mean that I think they are doing it all perfectly. They certainly should have a service status dashboard for their backend, so that the forecast.io guys could have pointed at Apple as the culprit with authority.
- natch 12y agoApple counts every duplicate radar as a vote for getting the issue fixed, so at least your filing of these wasn't wasted, assuming they were good issues.