3 ms·

This isn't a great answer, because there _is_ some literature to point to concerning how feedback (bugs and otherwise, regarding engineering) is handled at Appl

This isn't a great answer, because there _is_ some literature to point to concerning how feedback (bugs and otherwise, regarding engineering) is handled at Apple: https://www.corbinstreehouse.com/blog/2019/03/the-sad-state-of-logging-bugs-for-apple/?cat_id=86&order=DESC https://www.corbinstreehouse.com/blog/2019/03/the-sad-state-... The game that Apple's dev evangelism needs to play is the same one that MSFT/Google/etc play. Apple gets a free pass because they've had a largely devoted (almost cult-ish) fanbase of software developers (of which I count myself). They're starting to piss them off, though, and that has cascading effects. Lobbing things over the wall doesn't work anymore.

saagarjha 7y ago
If you read the article (I'm generally aware of the issues mentioned, FWIW), there isn't really much it tells you to do other than file bugs.
- Klonoar 7y ago
  I did read the article, considering I linked it in the first place. The snark isn't necessary. The ending of that article is a very resigned "this is all you can do. This is why it's this way, though.". The article is absolutely a criticism of how the bug process works. The entire point of all of this is that Apple needs to play the game better. You have a weird habit of popping up in every single thread to defend them, and I've noted your past associations with them in other threads, so I'll probably not bother responding to this further.
  - saagarjha 7y ago
    > I did read the article, considering I linked it in the first place. The snark isn't necessary. I meant this more as "if you go back and read the article, looking for the part I mentioned, since you may have missed this", which I included because you said my answer wasn't really great "because of so and so" even though it basically just restated what I had said. I know about the problems you're mentioning are: you know how I would. > The ending of that article is a very resigned "this is all you can do. This is why it's this way, though.". The article is absolutely a criticism of how the bug process works. > The entire point of all of this is that Apple needs to play the game better. You have a weird habit of popping up in every single thread to defend them, and I've noted your past associations with them in other thread Again, I'll freely admit I generally lean towards Apple because of the amount of time I've spent associated with the platform/tools/company, but I'm not disagreeing here: I'm with you 100%. As Corbin notes, however, filing bugs is more likely to get your issues noticed (and possibly responded to) than posting it four comments deep on a thread that admittedly has a higher-than-normal chance of getting clicked on by an Apple engineer. I guess if you know an engineer you might be able to see if they can institute change, but even then I'm not sure that would help much. Getting articles like these on the front page of Hacker News regularly might, though…

saagarjha 7y ago

If you read the article (I'm generally aware of the issues mentioned, FWIW), there isn't really much it tells you to do other than file bugs.

Klonoar 7y ago
I did read the article, considering I linked it in the first place. The snark isn't necessary. The ending of that article is a very resigned "this is all you can do. This is why it's this way, though.". The article is absolutely a criticism of how the bug process works. The entire point of all of this is that Apple needs to play the game better. You have a weird habit of popping up in every single thread to defend them, and I've noted your past associations with them in other threads, so I'll probably not bother responding to this further.
- saagarjha 7y ago
  > I did read the article, considering I linked it in the first place. The snark isn't necessary. I meant this more as "if you go back and read the article, looking for the part I mentioned, since you may have missed this", which I included because you said my answer wasn't really great "because of so and so" even though it basically just restated what I had said. I know about the problems you're mentioning are: you know how I would. > The ending of that article is a very resigned "this is all you can do. This is why it's this way, though.". The article is absolutely a criticism of how the bug process works. > The entire point of all of this is that Apple needs to play the game better. You have a weird habit of popping up in every single thread to defend them, and I've noted your past associations with them in other thread Again, I'll freely admit I generally lean towards Apple because of the amount of time I've spent associated with the platform/tools/company, but I'm not disagreeing here: I'm with you 100%. As Corbin notes, however, filing bugs is more likely to get your issues noticed (and possibly responded to) than posting it four comments deep on a thread that admittedly has a higher-than-normal chance of getting clicked on by an Apple engineer. I guess if you know an engineer you might be able to see if they can institute change, but even then I'm not sure that would help much. Getting articles like these on the front page of Hacker News regularly might, though…