There are many things that would be in Apple's interest to do, but they aren't so that's a complete non-argument.
I think it's a very valid question to ask, as many open source projects I've seen in the past that had to interface with Apple on the developer tooling front had to go through constant pain, as Apple isn't willing to e.g. provide references for certain .plist files, forcing many project to try and reverse-engineer what they do. More precisely there are usually people inside Apple willing to do that, but incapable to do that due to internal structures that result in a lack of clearly defined ownership.
So given that, I would say that if/once the original contributor of this PR moves on(/is made to move on) from that project, there is a good chance that this would also mark the end of cooperation from Apple's side.
alt Hacker News
There are many things that would be in Apple's interest to do, but they aren't so that's a complete non-argument.
I think it's a very valid question to ask, as many open source projects I've seen in the past that had to interface with Apple on the developer tooling front had to go through constant pain, as Apple isn't willing to e.g. provide references for certain .plist files, forcing many project to try and reverse-engineer what they do. More precisely there are usually people inside Apple willing to do that, but incapable to do that due to internal structures that result in a lack of clearly defined ownership.
So given that, I would say that if/once the original contributor of this PR moves on(/is made to move on) from that project, there is a good chance that this would also mark the end of cooperation from Apple's side.