> but several browser tabs and Electron/WebView apps running just fine on an early 2010s PC I employ.
"My car runs fine with the five anvils in the trunk" isn't the argument you're looking for.
Performance isn't the only problem with Electron either. Electron apps fail to integrate with native system components both from look and feel and accessibility aspects like incorrect zoom levels on HiDPI displays etc. They are even worse than browser tabs in that manner.
> I don't see an XAML based C# .NET desktop app performing marginally better than an equivalent well-written Electron app either
RAM usage would be at least an order of magnitude different. Nothing to do with how well-written it is either. It's inevitable.
Well, we're in the anvil business. Unless someone pulls the cart himself using C++ and MFC, similar amounts of oat will be consumed to get to our destination. Based on my empirical observations, WinUI 3 with C# eats memory like a horse. I'm willing to stand corrected with more data.
Platform integrity and accessibility are the real concerns with Electron. What is the solution, though? Does anyone still have time and patience for the byproducts of WinDev vs DevDiv power plays, even at Microsoft?
"My car runs fine with the five anvils in the trunk" isn't the argument you're looking for.
Performance isn't the only problem with Electron either. Electron apps fail to integrate with native system components both from look and feel and accessibility aspects like incorrect zoom levels on HiDPI displays etc. They are even worse than browser tabs in that manner.
> I don't see an XAML based C# .NET desktop app performing marginally better than an equivalent well-written Electron app either
RAM usage would be at least an order of magnitude different. Nothing to do with how well-written it is either. It's inevitable.