[nottorp]

> Slack is currently eating 600MB of my RAM, for something I check maybe once an hour.

You forgot about the times when two or more of the electron applications you run because you have no other option decide to take 20% CPU each or more.

Even if you make it a point of pride to run a computer that eats power measurable in kilowatts per hour, that's bad when on battery at least.

And from the article:

> One of the main core differences with Tauri is that it uses a Webview instead of using chromium like in Electron.

What's the difference? It will still end up eating all that ram and needlessly refreshing the cat gifs someone posted a day and a half ago.

[jraph]

> What's the difference?

The code of the web engine can be shared among several apps, instead of each of them having its own copy in RAM, making it less of an issue when having several of them.

If each of them don't abuse RAM usage of course.

Which is a big if of course.

[_piif]

Only if they make use of the same version of electron. Also apps tend to statically link their libs nowadays to reduce the amount of runtime dependencies from what I've seen. And I'm pretty sure apps distributed through flatpak and the like come with their own copy of the corresponding .so and won't share anything either - unless I'm wrong and electron does get shipped in a shared runtime.

[nottorp]

The .so is shared. All those uncompressed cat gifs, no.

I'm not familiar with internal browser architecture, but do they make at least a token effort to not render/run attached javascript for elements that are not currently in view?

I haven't measured, but my gut feeling is Electron apps go extremely crappy when you have like 30 memes in a row in a chat channel and make the mistake of switching to it.

Edit: hey, what happens when you open a 500 M log file in vscode?

[pwdisswordfishc]

There is not such thing as ‘attached javascript for elements’.

[nottorp]

There should be. So it can be turned off when the element is not visible.