Hacker News Reader

Hacker News

Comment by biohazard2 | Hacker News Reader

Parent Full thread

biohazard2

I can think of multiple ways to pass the message to Electron developers:

- Open a GitHub issue explaining those private APIs shouldn't be used.

- Even better, open a PR fixing their use.

- Make those API calls a no-op if they come from an Electron app.

- Fix those API calls not to grind the OS to a halt for a seemingly simple visual effect.

- Create a public API allowing the same visual effect on a tested and documented API.

Choosing to (apparently violently) downgrade the user experience of all Electron app users, without a possibility to update at the launch day, if a deliberate decision and not an overlooked bug, is a rather shitty and user-hostile move, don't you think?

View on HN

> - Make those API calls a no-op if they come from an Electron app.

Long-term, this is a maintenance nightmare. These hacks can stick around for decades, because there's no backpressure on downstream to actually fix things. It's not about "team velocity", it's about keeping yourself sane.

> - Open a GitHub issue explaining those private APIs shouldn't be used.

> - Even better, open a PR fixing their use.

Apple has a history/culture of secrecy. Whenever they provide public source code, it's a dump thrown over the fence. There is most likely some team inside that actually cares, but they can't "just" open an issue. My guess is that this is their message.

> [...] is a rather shitty and user-hostile move, don't you think?

Yes, I agree, the general direction they've been taking has been increasingly user-hostile for a very long time; let alone the developer story.

But sometimes there's also a perfectly reasonable excuse, from both "technical" and "organizational" POV. That's just my take, a skunkworks effort to get Electron to fix their crap. I would do the same.

The beta has been accessible to the public including the electron devs for 2+ months.

How nice of Apple to take a huge UX/PR/User Satisfaction hit just to send a message.

But I also blame users for using crappy electron apps ;-)

Apple is consistent in their warnings to not use private APIs, and especially don't override them for custom implementations which is what Electron does here.

The _cornerMask override was a hack that shouldn't ever have existed in the first place, and it's not the only use of private APIs in the electron code base.

Apple is very clear about how they want you to make software for their OSes. It's 100% on electron that they choose to do it this way regardless.

I'd go as far as to say Electron itself is a hack that shouldn't exist, but sadly everyone has decided it's the only way they are going to make desktop software now.

This mindset is not conducive to loving your customers.

To be clear, Electron themselves fixed the bug quite quickly; but many Electron apps haven't pushed a version that vendors in the fixed version of the Electron runtime.

(And shit like this is exactly why runtimes like the JVM or the .NET CLR are designed to install separately from any particular software that uses them. Each of their minor [client-facing-ABI compatible] versions can then be independently updated to their latest OS-facing-bugfix version without waiting for the software itself to ship that update.)

Reply on news.ycombinator.com