4 ms·

So to me, the issue with Electron is that I'm already running Chrome, so I should be able to take advantage of that. In particular, if I have N electron apps, I

So to me, the issue with Electron is that I'm already running Chrome, so I should be able to take advantage of that. In particular, if I have N electron apps, I want 1 Chrome running. I don't want to run certain applications inside the browser, I want the separate app icon, etc. Is there anything that is being done in Chrome/FF to support that kind of thing? That way it's up to the site consumer's preference how they wish to consume the app, by having a native browser consumer and not starting their own little Chrome each time. And for the developer, they're basically shipping "containerized" code around, modulo some features being unavailable in browser vs native, which could be feature detected.

pjmlp 8y ago
Yes, PWAs. That is how it should be.
WhitneyLand 8y ago
“I want 1 Chrome running” Why? To save a little disk space? There are a lot of downsides to that. Microsoft thought DLLs were a good idea once. I know Chrome has better isolation but it’s still not as idiot proof and most importantly, as cheap to support as having your own totally independent app. If a user contacts you with a bug, you immediate know for a fact it has nothing to do with any new chrome update or possible problems chrome may be having and vastly narrow down the problem space.
- easytiger 8y ago
  Given that chrome gives each tab its own heavy weight forked process, it is also pretty irrelevant conceptually. OP didn't explain what advantage he thought he'd get out of it being the same process he already runs other than saving some MB of exe cache. Perhaps that's all he wants. Either way these solutions are all rubbish.
- wishinghand 8y ago
  To save RAM usage and preventing constant cache thrashing.