4 ms·

What would be the disadvantages of just using a custom build of firefox for apps that bundles non-sandboxed libraries as needed? So for example, firefox.exe co

What would be the disadvantages of just using a custom build of firefox for apps that bundles non-sandboxed libraries as needed? So for example, firefox.exe could actually be built to be my app.exe, with the generic browser UI replaced with specific app menus. The build could have options for bundling any library, or provide a simple OS essentials abstraction library with a web sockets or local web server http interface. It would be a single use custom UI browser “app” with the same potential power as an OS native app but easily portable. Benefits - I think FF is a ~50MB download so after stripping out a little generic browser functionality, simple utility apps should be about the same - One of the biggest problems with these ideas normally is the actual multi-platform deployment can become the hardest part of a cross platform app, yet FF has a polished multi platform install/setup solution already fully figured out and maintained.

jitl 8y ago
This is exactly what Electron / CEF is, except the tooling already exists for CEF, and there’s already a large ecosystem of libraries.
- WhitneyLand 8y ago
  There is theory and practice. similar concepts, but for so long we’ve heard big hassles with electron solution real life deployment solutions (some companies only don’t even deploy electron multi platform, if it were that simple more would). Also with memory usuage which was mentioned elsewhere in this discusssion. The idea is maybe it could be done better. On the other hand maybe Electron has made great strides over last year or so, it would depend on how much progress has been made. Cross platform code is great but in the end doing that while getting something out the door end to end multiplatform as fast as possible is key, while at the same time not having performance significantly worse than it would normally be for the same code in an off the shelf browser.

jitl 8y ago

This is exactly what Electron / CEF is, except the tooling already exists for CEF, and there’s already a large ecosystem of libraries.

WhitneyLand 8y ago
There is theory and practice. similar concepts, but for so long we’ve heard big hassles with electron solution real life deployment solutions (some companies only don’t even deploy electron multi platform, if it were that simple more would). Also with memory usuage which was mentioned elsewhere in this discusssion. The idea is maybe it could be done better. On the other hand maybe Electron has made great strides over last year or so, it would depend on how much progress has been made. Cross platform code is great but in the end doing that while getting something out the door end to end multiplatform as fast as possible is key, while at the same time not having performance significantly worse than it would normally be for the same code in an off the shelf browser.