3 ms·
Underrated factor IMO: > consistency with the UI conventions of a given desktop operating system Desktop conventions sort of exist for macOS but definitely do
by n8cpdx 5y ago
Underrated factor IMO:
> consistency with the UI conventions of a given desktop operating system
Desktop conventions sort of exist for macOS but definitely do not exist for Windows or Linux.
I won’t go into Linux because I don’t want to deal with that energy right now, but Windows is an absolute mess:
- WPF
- WinUI (2 and 3, totally different)
- WinForms
- MFC/Etc
- WebView2 (basically electron but being promoted as first class for some reason)
Even within Microsoft’s own apps they can’t agree on UI conventions (e.g. are things round or square - Maps and other built ins use both).
On web you have to totally create UI from scratch, which usually means bootstrap or your company’s design system. Turns out windows desktop is basically the same, because apps have to create their own look from scratch - even Microsoft’s own native apps (Office, Visual Studio, etc) don’t use out-of-the-box UI.
Of course for new work Microsoft is mostly using Electron or WebView2, which should be telling (Teams, VS Code, etc). On the developers side, they’re pushing blazor, which is relying on electron or webview2 for the desktop story.
- klabb3 5y ago> WebView2 (basically electron but being promoted as first class for some reason) Rendering a webview using the OS should have much lower disk & memory overhead than bundling chrome + node. In theory, there's no reason it should be higher than the cost of a tab in a browser. I'd love to see some benchmarks though.