4 ms·
I think it's more accurate to compare Node to C++, compare NPM to apt/yum/etc+CMake, and compare something like Electron to Qt. Of course, your point still sta
by quacker 9y ago
I think it's more accurate to compare Node to C++, compare NPM to apt/yum/etc+CMake, and compare something like Electron to Qt.
Of course, your point still stands. But's a tradeoff. C++/Qt has a ton of compile-time bloat, while Node/Electron has runtime bloat (see the Slack client using hundreds of megs of ram). And you can use bindings, like PyQt, where you have Python/Qt and then you get Python's dependency management.
- thehardsphere 9y agoCompile-time bloat and runtime bloat are not equivalent. Runtime bloat inflicts pain upon users and therefore is usually worse.
- softawre 9y agoYes.. Don't you think that's why he bothered mentioning the words "runtime" and "compile-time"?
- thehardsphere 9y agoWell, the way I read what he wrote was that he was suggesting that bloat is bloat wherever it happens so that it's all a wash.
- dirkc 9y agoWhen I had the revelation I was thinking about the whole npm, bower, gulp, webpack toolchain. Comparing C++ to Node or Python doesn't help me. If I could write Python that run in the browser I wouldn't be commenting here.