Hi Mark, > On Nov 29, 2016, at 2:02 PM, Mark Lucas <catkee...@aol.com> wrote: > > >> On Nov 29, 2016, at 3:00 PM, carbon-dev-requ...@lists.apple.com wrote: >> >> the fact that it existed through at least one major OS release prior to >> being reported indicates that it’s not causing big problems for lots of >> people - if it were, we’d have a lot more reports. > > Hi Eric, > > Please don’t take this personally
Not at all! I hope this thread is useful for both developers and any Apple engineers who might still be reading it, to see a new perspective from the other side. > but while that's apparently a common perception at Apple I feel compelled to > respectfully point out that it’s not even remotely true… > For example no matter how many users of our authoring tool experience a given > problem, you’re vanishingly unlikely to receive more than one bug report > documenting it. That’s because few of these folks have developer accounts, > and fewer of those who do will ever file a bug themselves about it (because > they’re busy, and without the source code they literally have no clue what’s > going wrong, where, or why, and use these tools specifically to avoid needing > to). So anything I file a report against (unless explicitly noted otherwise) > typically affects hundreds or thousands of loyal longtime Mac developers all > over the world. But if I can’t fix or work around a problem in Apple’s code > they complain only to ME, not to you (and I file the aforementioned lonely > report, which typically sinks without so much as a ripple). I see your point. It is certainly true that end-users who aren’t developers are much less likely to be filing Radars. They usually have two other avenues to report problems: either back to the developer of their software, or to AppleCare. We certainly get reports from AppleCare when a noticeable number of users are reporting the same problem. However, I want to emphasize that my major goal here is to explain the situation as it currently exists, so that you can more effectively work with Apple to get what you want. The simple fact is that there are far too many bugs filed every day for Apple to fix every one of them. We must prioritize. We have no choice. Not every bug will be fixed. And Radar, while it is a rough measurement, is still the most reliable measurement we have so far. I think many people inside Apple would agree with you that Radar counts are a blunt instrument. As blunt as it is, though, it is still the tool that we use every day to prioritize bugs. It’s certainly possible for a developer to provide data in a single Radar that can make the case for a prompt fix. For example, if you were able to survey your users and determine that out of 10,000 users, 8,000 of them were impacted by a particular problem, and that was preventing them from upgrading to a new release, then including that data in a Radar would be very useful. Obviously you, as the direct point of contact for the users of your software, are in a much better position than we are to provide data about the impact of a bug on your user community. -eric _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/carbon-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
