It’s weird to me that they consider GTK a “native” implementation — GTK is a whole [opinionated] layer of abstraction on top of the native interfaces.

It’s native in the sense that it’s not Electron, or Java, but it’s still a layer of abstraction which introduces all sorts of quirks.

A few other ugly quirks in Linux:

- It doesn’t respect the user’s configured fonts. - Clipboard support is inconsistent. - The GTK4 UI is quirky, and has silly slow animations in situations which don’t make sense.

The first two sound like more serious issues, and I’m surprised that others haven’t found them dealbreakers.

What’s the other option?

> SafetyNet […] provides an API for applications to verify the app is running in a verifiable and locked down environment.

FTFY

> Google doesn't have control of Chromium though.

They do. If they merge DRM into it tomorrow or something alike, it trickles down to all users of Chromium and Google Chrome.

You can build _a fork_ of it. But the enormous majority of the masses don’t use your fork — they use upstream.