It's weird for the author to mention Mac window buttons and corner radius as reasons to use Electron, because while the main content of Electron app windows is HTML, the Electron windows themselves and the window chrome are native, with the same buttons and corner radius as other apps on the system.

Electron is a native wrapper for web content. The wrapper is still native.

> Native APIs are terrible to use, and OS vendors use everything in their power to make you not want to develop native apps for their platform.

I'm honestly not quite sure what the author means here.

Web APIs are equally “terrible” in my opinion. In any case, you have to release an Electron app on Mac the same way you release any native app on Mac. The benefit of using web APIs is not that they are non-terrible but that you can share the same code as your website. And of course you can more easily find web developers than native developers. But that has nothing to do with whether or not the API is terrible. It’s just supply and demand.

I’ll take AppKit and autolayout any day over CSS, ugh. CSS is the worst.

> with the same buttons and corner radius as other apps on the system

I just checked: No, the corner radius is different. I'm personally not very bothered by that, but it's just empirically true.

> Electron is a native wrapper for web content. The wrapper is still native.

In my view, the problem isn't that it's a wrapper, but rather that it's that it's a bad wrapper of a bad runtime (i.e. the incredibly bloated JS/web stack).

UIKit etc never made sense to me after years, CSS also didn't make sense, but right out of the box I understood React. And with hooks, it's way less boilerplate than the UIKit ways.

Separate from that, Apple doesn't seem to mind breaking native macOS apps, to the point where most devs treat native code like a liability on Mac but ok on Windows.