Live data from Hacker News

Rationales for Swift standard library designs

github.com

11–13 of 13 posts

Re: Rationales for Swift standard library designs

#11
post #7
post #6

Earlier quoted context omitted.

Gruber brought up how in Apple Maps, if you suggest a correction, you are eventually informed when the fix is made. However, with Radar, it is just a blackhole. You file your report and an awful lot of bugs, no matter how well written or even if they have example code, they will never hear back again about it. He said that this was a negative feedback loop because developers will end up submitting less bugs because o…

It's bad, but not quite a black hole. I have had the occasional feedback out of it, of the limited form "this should be fixed in the release that just came out. Please retest"

Trouble is, that "please retest" message is boilerplate that's often sent out regardless of whether any work is done in the offending area.
Post reply on HN