That's Node (V8) and Electron (Chromium and all its dependencies) for you.

Maybe, just maybe, we should just bundle Node and Electron into a package, install that as a shared library (similar to the way .NET and Java are installed) and then just ship, in the installer, a tool that downloads those if not already installed?

Would save a lot of memory and time for everyone.

Electron is moving pretty quickly (and breaking APIs) at this point so you'd end up with just as many versions of the shared library as you would copies in applications.

Breaking APIs is not generally good either.

But if a single newsreader contains more code than a full PlayStation game, you know something’s wrong.

This is just Wirth’s Law in action.

The very fact that we 'do not break APIs' is one of the reasons that this newsreader is 100+ MB. If Google Chrome wasn't 4,490,488 lines of code designed across years of development to, well, _support old web APIs_ -- then it would likely be much smaller. :)

Well, and, as the parent said, even with this you still can’t use the same version of the library even for a few months. That’s the worst out of both worlds.

How is it 100 MB? RAM or disk space?

After checking RAM usage, I'd say both.

256MiB RSS when active, hahaha. Chrome isn't memory efficient, but this takes the cake.

Disk space

Yeah, unfortunately the app bundled with a Chrome. But, the upside is it's implemented in HTML/CSS/JavaScript and it's hackable :)

Did you consider making a simple Chrome app of this?

Perhaps, that will come. We need to learn more about how people use it, and get more feedbacks.