News for hackers. Stuff that matters.
Re:JavaScript is Eating the World by quacker on Thursday August 24, 2017 @01:11PM (#15091943)
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.

Re:JavaScript is Eating the World by thehardsphere on Thursday August 24, 2017 @02:09PM (#15092517)
Compile-time bloat and runtime bloat are not equivalent. Runtime bloat inflicts pain upon users and therefore is usually worse.
Re:JavaScript is Eating the World by softawre on Thursday August 24, 2017 @02:38PM (#15092766)
Yes.. Don't you think that's why he bothered mentioning the words "runtime" and "compile-time"?
Re:JavaScript is Eating the World by thehardsphere on Thursday August 24, 2017 @06:27PM (#15094597)
Well, 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.
Re:JavaScript is Eating the World by dirkc on Thursday August 24, 2017 @04:38PM (#15093840)
When 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.