Im not sure if people are getting the biggest problem in electron desktop apps.

Its RAM usage not the disk!!

Why are they all making the same thing in different ways?! I have never worked on an electron app where the executable size was an impediment to the business. Its always the RAM/CPU usage. If we are going to work on the same webviews like electron and others, how will this make any difference?

▲

mpweiher 6 hours ago | parent | next [-]

Easy: the problem with memory is not the WebView nor is it displaying HTML using that WebView. The problem is the layers of layers of JavaScript (frameworks) running in that WebView when using Electron or the like.

I am working on something similar, HTMXNative as part of a bigger idea called interscri.pt that can use either WebView or native for rendering and the difference in memory consumption is somewhere between minimal (or even undetectable) and modest.

From a baseline that's also modest by current (native) standards.

	▲	vijaybritto 4 hours ago \| parent [-]
		I am cursed that I always have to work on legacy products that were built many years ago and didnt consider these things. I hope we eventually get a good/simple language/framework that can compile to native code. Even react native for mac/windows is good enough now.

▲

cosmotic 7 hours ago | parent | prev | next [-]

Using the system webview theoretically saves memory. Though it's still not great.

▲

Bolwin 7 hours ago | parent | prev [-]

Cause they all share one webview. Electron apps each run their own version of chromium