> The only reason it should be a "jank interface" is because the browser makers haven't been doing all they can to make browsers capable, which is basically what you are arguing against. That's circular logic.
What I'm arguing against is the idea that any 'universal' target will inherently feel out of place on every platform, that writing multiple GUI frontends targeting only the platforms that actually matter for your application isn't nearly as hard as developers make it out to be, and that ultimately native GUI frontends will make user's lives much better because they fit the system they're a part of.
> But the main point is, why would you want to invest all your development efforts into a proprietary API that locks you in and is under the control of a single company?
You're not locked in to anything, you structure your code such that the platform-specific portion can be swapped out for each platform. This is hardly a new concept.
What I'm arguing against is the idea that any 'universal' target will inherently feel out of place on every platform, that writing multiple GUI frontends targeting only the platforms that actually matter for your application isn't nearly as hard as developers make it out to be, and that ultimately native GUI frontends will make user's lives much better because they fit the system they're a part of.
> But the main point is, why would you want to invest all your development efforts into a proprietary API that locks you in and is under the control of a single company?
You're not locked in to anything, you structure your code such that the platform-specific portion can be swapped out for each platform. This is hardly a new concept.