31–36 of 36 posts
This has been solved already: http://openradar.appspot.com If you file a new bug with Apple, publish it here as well. No more black hole, you can see what others have already posted. You can even see what duplicates are about (if the original bug was also at open radar).
This has been solved already: http://openradar.appspot.com If you file a new bug with Apple, publish it here as well. No more black hole, you can see what others have already posted. You can even see what duplicates are about (if the original bug was also at open radar).
Interesting usage of the word "solved", there.
There's already an effort to do this: http://fixradarorgtfo.com/ 500+ developers so far have submitted this to Apple.
This has been solved already: http://openradar.appspot.com If you file a new bug with Apple, publish it here as well. No more black hole, you can see what others have already posted. You can even see what duplicates are about (if the original bug was also at open radar).
Interesting usage of the word "solved", there.
I once had an interesting experience when visiting Apple. I was telling a DTS engineer about a gnarly bug in the Cocoa text system I had found (certain text editing sequences would silently corrupt the undo stack; user might not notice until they accidentally did a select-all and delete, and then tried to undo to get their novel back). I never got any feedback on this bug at all (just like always). But, this Apple gu…
As a someone who's filed a few Radar issues over the years, I understand that the lack of feedback is frustrating, but I find it absurd that the way to fix that is to withhold the bug reports that help improve the software we use and develop for daily.
I once had an interesting experience when visiting Apple. I was telling a DTS engineer about a gnarly bug in the Cocoa text system I had found (certain text editing sequences would silently corrupt the undo stack; user might not notice until they accidentally did a select-all and delete, and then tried to undo to get their novel back). I never got any feedback on this bug at all (just like always). But, this Apple gu…
I find the toilet analogy to be flawed. Sure you don't fix their toilets for free, but you would certainly let someone know if you used one of their facilities and found it to be clogged or otherwise malfunctioning. As a someone who's filed a few Radar issues over the years, I understand that the lack of feedback is frustrating, but I find it absurd that the way to fix that is to withhold the bug reports that help im…
Now, if it was instead the toilet at a restaurant or other venue that I frequent, where I am welcomed and treated with respect, then of course I would alert the staff to their problem.
But a developer's relationship with Apple is much more the former than the latter. (I file really awesome bug reports for other software I use, like OmniGraffle or Arq.)
It's also important to note that I didn't begin with this attitude; I ended up with it after filing dozens of detailed Radar bugs over the years, and evaluating how shitty the response from Apple is.
As others have pointed out, if a developer spends 5+ hours isolating a crippling bug in your shit[1], and filing it with a repro case[2], and you don't even have the courtesy to let them follow changes to the bug when it's marked as a duplicate, then well... you're kind of a rude and arrogant asshole. So developers become less likely to keep performing this service for you... unless they really really really want the bug fixed.