This summarizes Apple's attitude to developers. Eventually, you'll run foul of some obscure nonsensical Apple policy, and Apple will not hesitate to show you the finger. And Shame you for your dev choices.
Apple's policy towards private APIs has been known for years.
Apple is roadblocking the use of private APIs, not languages. Or interpreted another way, they're roadblocking frameworks, not languages. This is true whether you're using Javascript, Swift, or C. This rule has been in place for years.
Which is not a homogenous group, both in ideals and for why they'd upvote a submission like this.
> this rejection, and it's backing policy to be nonsensical
They're different things. I personally think the rejection is perfectly sensical in the context of the backing policy, with which I don't fully agree.
When you are writing any software that has a public API you should feel no obligation to change the functionality or completely remove a private method without warning.
[1] I refuse to call it a private API. An API is public documentation of the inputs and expected behavior of a dependency. It should be a completely black box how that functionality is implemented.
This is not Apple "watching out" for the developers, no matter how much you spin it
Apple will only listen if it hits their bottom line.
If you can't avoid Apple's stores then make damn sure you fall in line as they effectively own you.