4 ms·
I’m curious what the resulting package would look like. Like you’re including the v8 runtime but not chrome itself (A la electron). I suspect it would be smalle
by matthewfcarlson 5y ago
I’m curious what the resulting package would look like. Like you’re including the v8 runtime but not chrome itself (A la electron). I suspect it would be smaller but no idea how much smaller.
- joaodasilvaz 5y agoIt's quite a bit smaller though I'm not familiar with how big Electron is nowadays. The largest part is, by far, v8; I think there's room to remove unused code there. You can see the size of the binary in the GitHub Actions builds: https://github.com/windowjs/windowjs/actions https://github.com/windowjs/windowjs/actions Each build workflow has a "Binary size" step at the end, that outputs the binary size, size after stripping, and size after using UPX. Here's what the latest build got: * Windows: 6,639,616 bytes (19,523,072 before UPX) * macOS: 8,196,112 bytes (23,431,800 before UPX) * Linux: 8,186,668 bytes (28,679,960 before UPX and stripping, 22,346,264 bytes after stripping)