3 ms·
That actually sounds kinda impressive, considering [0] says a minimal standard Qt hello world app is ~5mb and stock node.js is ~100MB. I'm curious what kind of
by lhorie 6y ago
That actually sounds kinda impressive, considering [0] says a minimal standard Qt hello world app is ~5mb and stock node.js is ~100MB.
I'm curious what kind of magic is happening where node.js is in the picture yet the executable comes out at ~20MB. Is it simply a bundle of wrappers for most of Qt with Node.js being required to be installed separately? Is it purely UPX compression?
[0] https://stackoverflow.com/questions/450455/minimal-qt-executable-size https://stackoverflow.com/questions/450455/minimal-qt-execut...
- lhorie 6y agoPoked a bit more. It seems the 20Mb claim is indeed mostly only about runtime memory, and doesn't translate to equivalent disk usage. The entry point in ther starter kit calls qode (a fork of node), which talks to qt via napi (node's API for c++ bindings). It can be distributed as binaries via the *-deployqt toolchains. So for distributable binary size in disk, we're probably looking at something in the ~100mb range with no UPX shenanigans. So, tl;dr not as magical as I initially assumed. The trade-off between "bloat" vs ability to use web paradigms feels like a reasonable one. Overall pretty cool stuff.
- jiofih 6y agoA node OS X build is 13mb, 20mb on Linux.
- lhorie 6y agoAre you looking at tar.gz files in nodejs.org/dist? Those are compressed. "Get info" on the actual binary on my OSX gives me a number closer to 80MB.