The post shot to #1 because there are a lot of Javascript developers that see Electron as a gateway into apps they would otherwise be unable to develop. There's a lot of interest in whether or not that door closes.
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.
You must be chugging the koolaid to believe developers LOVE Apple's policies, or enjoy getting their hard-work rejected by a bot, or getting shamed by an overzealous Apple employee on HN. Developers are homogeneously unappreciative of Apple's treatment of them. They just don't have any leverage, or opportunity to negotiate
Who are you going to blame when applications start breaking because Apple removes or changes the functionality of a private function? [1] without warning?
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.
Blame the developer? Which is why, when an app breaks on the Mac store or app store, users pound the app with 1-star reviews. Even if the breakage happened from a platform (iOS or MacOs or Android) bug.
This is not Apple "watching out" for the developers, no matter how much you spin it
