> On Nov 29, 2016, at 3:00 PM, [email protected] 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, 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). Due to their work environments most of these folks are not ‘bleeding edge’ adopters either, so such a bug not being officially reported for an entire OS release indicates little to nothing about how catastrophically show-stopping it may ultimately prove to them and their users/employers. That can (and does) delay or prevent entire organizations from updating their OS or buying new machines that fatally break legacy in-house apps they depend on (which often are a principal anchor to the Mac platform) that upgrading would force them to rewrite from scratch. Not to mention SERIOUSLY pissing them off, and forcing them to question their decision to live in a walled garden… And I can’t possibly be the only one in this position, which means there’s undoubtedly a whole flotilla of such ‘big problems for lots of people' that are effectively invisible to ‘radar’ yet still have a significant and ongoing negative impact on Apple’s customer/developer (ahem) loyalty and bottom line. Just sayin’... <<climbs down off soap box>> -Mark _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/carbon-dev/archive%40mail-archive.com This email sent to [email protected]
