4 ms·
then why still use Electron? why not just c++-backend with an embedded http server for frontend that uses the browser
by ausjke 6y ago
then why still use Electron? why not just c++-backend with an embedded http server for frontend that uses the browser
- swsieber 6y agoSecurity? Seems like any webpage could make calls to your program, no?
- emodendroket 6y agoThat's just standard CSRF stuff isn't it
- beached_whale 6y agoTheres a lot of people proficient in Electron. It also handles IO I assume
- pjmlp 6y agoAKA Chrome APIs.
- beached_whale 6y agoThanks, I haven't worked with it but assumed.
- akritrime 6y agoFor many users that can be an alien experience. For most non-technical people, browser is still primarily for accessing contents on the web and switching them to a user experience where you have to start a backend server locally and then access it via the web browser can just feel hacky and even a bit off-putting.
- pjmlp 6y agoYou can do that perfectly transparent, the executable just starts the user standard browser. It was a standard practice for some applications in the .com days. Electron is just another example of the disease making Web == ChromeOS.
- the_only_law 6y agoI would assume for the same reason that they don't just use a normal web app. They want the packaging of a native app.
- pjmlp 6y agoPackage as native app, it starts the user browser pointing it to localhost into its builtin server, plenty of examples during the 90's, e.g. CUPS printer management tools.
- emodendroket 6y agoI'm not sure the app ESR famously blew up for having a horrible UX is the example I'd point to to say it's not confusing.
- pjmlp 6y agoThat is the proper way of doing, but then some lazy devs rather code with Chrome APIs instead of Webs standards.