Abuse of private APIs means that your public API is incomplete. And that people dislike how your system behaves so much, that they're willing to muck with its internals.

▲

bigstrat2003 9 hours ago | parent | next [-]

No, it means that people think they know better than to listen to the warning.

▲

stalfosknight 10 hours ago | parent | prev [-]

No, it means some people are doing it wrong either because:

1. They don't know how to do it the right way

2. They can't be bothered to do it the right way

#1 I can understand. We all make mistakes as we learn and grow as developers. #2 is just arrogance / laziness on the part of the developer. Compounding it by blaming the platform owner that clearly and explicitly told you not to go that route is gross.

▲

cyberax 10 hours ago | parent [-]

[flagged]

	▲	epistasis 9 hours ago \| parent \| next [-]
		From the bug report: > It turns out Electron was overriding a private AppKit API (_cornerMask) to apply custom corner masks to vibrant views. > ... > By removing the custom _cornerMask override and associated logic, we allow AppKit to handle shadows with its default pipeline. This resolves the GPU spike while retaining shadows as expected. I'd say that most often usage of private APIs is because: 4. it probably shouldn't be done at all
	▲	stalfosknight 10 hours ago \| parent \| prev [-]
		I'll grant that their documentation isn't the best I've ever seen, but it is still on you if you reach for private APIs. Again, that is consciously choosing a shortcut you've been explicitly told not to use.