> I agree, but I think at least some of the animosity stems from how the author might not have been able to do this themselves if they wanted to What animosity

> I agree, but I think at least some of the animosity stems from how the author might not have been able to do this themselves if they wanted to What animosity? The animosity other people have on behalf of the author who has clearly said he has no beef with this series of events? If the author wanted to make algorithmic changes like the VS code team have done, I'm sure they would have been more than happy to discuss this on the open source issue tracker (which is very active). > just hurts to see after having been burned by Apple's private APIs blocking legitimate app developers from doing something Apple will release next cycle themselves, The big difference here being that the app developers are happy that this has happened, and they could have attempted to do this work because even though the APIs are private, the source is available and they readily take pull requests.