I think the point is that it's better to have something using the native widgets of your OS if possible. It carries much less footprint and it integrates with your OS much more nicely in the end. Webapps running in Electron is just becoming too commonplace.

That also means building a separate UI for every supported OS, which isn't usually feasible for a single developer.

Just an fyi, it looks like you need to include the www for the link to load.

Qt also isn't truly native (it renders its own UI components) and shares many of Electron's drawbacks, so it's only marginally better (and means you have to learn an entirely new platform if you're already familiar with web dev).

> marginally better

Not in terms of resources (CPU/RAM). It's way better than Electron.

I've done it.

I didn't say it's impossible (I've also done it), but for something that's not a full-time job/project, it's a lot of extra work that could be avoided by simply using Electron, especially if you are already familiar with web development but don't have any experience with any of the native platforms.

But the poster did say this was a full-time project.

And I don't believe that only having experience in web development is a good enough excuse for shoehorning web dev things everywhere else.

You're right, I missed the OP saying that. But I still disagree: prior experience with a platform is a great reason for using it. Maybe not for a company with lots of resources, like Slack or Microsoft, but definitely for a small team or individual developer. Any time you would have spent learning a new development platform can instead be spent building new features!