There are so many apps out there which take every shortcut they can to make it easier for developers regardless of the impact on users. On iOS, using things like react native instead of actually native code; on desktop systems, using Electron instead of any other toolkit.
I understand why, mind you; would VS Code or Slack have as much velocity of improvement if they had to individually manage GUI toolkits for each platform? Would VS Code be as extensible if the UI were built in Swift or Qt?o But the results are still there.
There are projects to try to make this /better/, like Tauri - Electron but using your system's built-in browser engine rather than shipping a new one, so that you don't have to have eight separate copies of Chromium loaded into memory - but they still need to reach feature-completeness and projects need to do a non-trivial migration, and then they need to test across multiple browser engines, etc., so it's still not the same.
Regardless, this is the situation we have right now; everyone figured that RAM capacity would continue to increase at the same rate as RAM usage, "it works on my machine" but it's a 32 GB Macbook, Chromium optimized for performance and not memory usage by assuming that each 'page load' would be short lived (browser behavior) rather than having one 'page load' run for hours or days (Slack, VS Code, Spotify).
Looking over the actual killer feature for Electron: running your existing web code with native features layered on top. I mean yeah Tauri does this too, but I think it's relatively rare for someone to decide "I'm going to build a standalone native desktop app in Electron because it's easiest," they're thinking "I already have this PWA that i can repackage with native features without maintaining a whole second UI."
I understand why, mind you; would VS Code or Slack have as much velocity of improvement if they had to individually manage GUI toolkits for each platform? Would VS Code be as extensible if the UI were built in Swift or Qt?o But the results are still there.
There are projects to try to make this /better/, like Tauri - Electron but using your system's built-in browser engine rather than shipping a new one, so that you don't have to have eight separate copies of Chromium loaded into memory - but they still need to reach feature-completeness and projects need to do a non-trivial migration, and then they need to test across multiple browser engines, etc., so it's still not the same.
Regardless, this is the situation we have right now; everyone figured that RAM capacity would continue to increase at the same rate as RAM usage, "it works on my machine" but it's a 32 GB Macbook, Chromium optimized for performance and not memory usage by assuming that each 'page load' would be short lived (browser behavior) rather than having one 'page load' run for hours or days (Slack, VS Code, Spotify).