|
I think you underestimate the impact these particular reviews are having for some, even if it's a minority. Apple has as much incentive here as they have with any customer complaints. If it's important enough to developers and genuinely impacts their product (aka products Apple benefits from in more ways than one) they know it will effect the relationship they have with Apple. Like with anything however, the problem needs to communicated. The more people who communicate the same issue, the more likely it will get attention. https://bugreport.apple.com/ is the place to start. Not blogs, not HN, not Twitter or anything else. If you want a problem you're having solved, start with filing a report in as detailed, and polite, a way as possible. Using blogs to bitch and complain about how Apple is ignoring an "obvious" issue, or how stupid they were to do things in such-and-such a way, is essentially counterproductive and being part of the problem rather than the solution. Using them to explain the issue, get a discussion around it going, coming up with solutions that work for you and fellow developers, and get additional reports filed, enhances the ability for Apple to respond with a genuine solution sooner rather than later. Sometimes they see the blogs and articles, but I'm sure it's more often they don't, so the trend I've seen over the last several years of vitriolic blogs being the first and only mention of a problem has, IMHO, really been disservice to the whole community. It's always taken much longer than I would personally like or understand, but with enough bug reports filed on a given issue I do see traction and changes come later on down the road. They may not always be the changes I explicitly requested or expect, but they do resolve the problems in one way or another. edit: grammar |