4 ms·
Because you might ship this to users and just having an app for them to click on and open is a lot more user friendly than telling people to type in some localh
by dewey 4y ago
Because you might ship this to users and just having an app for them to click on and open is a lot more user friendly than telling people to type in some localhost URL or open browser tabs with "cryptic" urls.
- pjmlp 4y agoJust have the application start the browser like daemons used to 20 years ago. Nowadays they can even send the PWA manifest to hide the browser appearance.
- dewey 4y agoAre we really arguing why someone might want to have a "native" app instead of a browser window? There's many reasons why someone might want to have that.
- pjmlp 4y agoYes we are, Web technologies belong in the browser. I wasn't impressed with MSHTML when it came up as Active Desktop, nor I am impressed with anything that followed suit.
- dewey 4y ago> Web technologies belong in the browser That ship has sailed a long time ago. These days sometimes whole operating systems are based on HTML based interfaces (LGs TV OS would be one example).
- pjmlp 4y agoWebOS applications don't ship a browser alongside them, they use what is already installed. Doing Web development alongside native since Web exists, hasn't made me like shipping browsers with applications (or Web views) any better during the last 20 years.
- solardev 4y agoThis framework does this same thing: > It does not embed a browser, so it is resource efficient. Instead, it uses the native rendering engine for the platform. On Windows, this is the new Microsoft Webview2 library, built on Chromium. https://wails.io/docs/introduction#native-elements https://wails.io/docs/introduction#native-elements