Re:Claude is an Electron App because we've lost native
by paulryanrogers on Tuesday March 03, 2026 @06:10PM
(#47240429)
Except the OS's don't even ship a consistent enough browser engine. (Standards be damned.) So apps ship their own browser over and over again.
Re:Claude is an Electron App because we've lost native
by zadikian on Tuesday March 03, 2026 @06:15PM
(#47240486)
Yeppp. Is there no way for Electron apps to use a shared engine if one is available?
Re:Claude is an Electron App because we've lost native
by paulryanrogers on Tuesday March 03, 2026 @06:20PM
(#47240532)
I think Tauri tries this approach.
Re:Claude is an Electron App because we've lost native
by edflsafoiewq on Tuesday March 03, 2026 @08:19PM
(#47241747)
Of course. Arch for example ships packages that use a shared system electron. But you'll often end up need multiple electron versions.
There's also stuff like lorca which shells out to an installed Chromium browser.
Re:Claude is an Electron App because we've lost native
by c01nd01r on Wednesday March 04, 2026 @11:28AM
(#47249889)
https://neutralino.js.org/
But I think even there itβs possible to encounter platform-dependent bugs - starting from view issues (you know, different OS can use different browser engines) and up to those related to system APIs.
The approach runs slower than a game written directly in assembly, but the cost to port to different architectures is much lower.
Sort of like Electron trades off native performance and look-and-feel to make multi-platform apps much more achievable.
IMO the OS vendors failed everyone by refusing to even attempt to agree on a common API for UI development, paving the way for web browsers to become the real OS and, ultimately, embedded browsers to be the affordable and practical way to be cross platform.