54 points thunderbong 2 hours ago 55 comments
cheschire 1 hour ago | parent
Electron's value prop has always been about having one team producing one app that is supported on multiple platforms with minimal additional effort.
This article does nothing to address that.
RunSet 45 minutes ago | parent
"Now you can have the cross-platform compatibility of a single-page application just by bundling Chrome."
zdragnar 20 minutes ago | parent
Not a great justification, but it made a bit more sense then.
tekla 44 minutes ago | parent
johnh-hn 30 minutes ago | parent
For a long time, and mostly out of frustration, I wanted to build my own stack of software around my vision. But the mammoth amount of effort it would require meant I never went through with it.
freecodeio 10 minutes ago | parent
hajile 3 minutes ago | parent
Google Chrome generally used around 25mb per tab in 2010. Today, that number is often 500mb or even 1gb.
Grombobulous 16 minutes ago | parent
Election predates WebAssembly by 5 years and hit the scene only one year after Rust was first created.
And just like JQuery, its time is coming to a close as better frameworks are available now that weren’t available back then.
s3p 14 minutes ago | parent
IshKebab 26 minutes ago | parent
I dunno if you've been living under an enormous rock, but they used AI to make this.
Grombobulous 17 minutes ago | parent
At the time Electron came out, there weren’t as many cross-platform UI frameworks available that they could have gone with.
You can see this with the comparison chart. GPUI effectively replaced Electron so the desktop app UI works across platforms. React Native is replaced with WebAssembly so that Rust can be the primary language across all platforms including mobile.
It seems like the new situation for Discord is rather elegant, and that none of this would have been available when it first came out.
accurrent 3 minutes ago | parent
The only way to ship the same code between linux, macOS, and Windows would have been to either use something like Qt or the JVM back in the 2010s. The JVM desktop stuff was super ugly and Java itself had become notorious (also if you wanted anything remotely interesting like webcam/microphone or multimedia access you'd still have to ship dynamic libraries). Qt required special packaging skills to ship to the end user especially if third party libraries were involved. Electron killed that by bundling chrome (and chrome has a huge api surface).
Today, I would argue the package management situation for a language like rust is a lot different. You dont have to cobble different DLLs together, you can just statically compile dependencies and cargo/rust do a pretty good job of making sure it's bundled with your app.
kryptonomist 1 hour ago | parent
r_lee 1 hour ago | parent
it would be absolutely awful
compared to chromium, it's really limited, like it's just always a compromise with these
we should instead figure out a way to do electron but better and make it easier to do the things you can do with e.g. React with native languages and frameworks
amelius 1 hour ago | parent
debazel 44 minutes ago | parent
If you just reimplement Electron in a native language then you get... Chrome, which is already written in C++. The majority of RAM usage in Electron applications is from the native parts of Chrome itself and a decent ~40 MiB chunk for the Node.js runtime.
caspper69 38 minutes ago | parent
edit: Avalonia is quite mature, with accessibility to boot.
the__alchemist 6 minutes ago | parent
airstrike 1 hour ago | parent
cpursley 48 minutes ago | parent
itopaloglu83 1 hour ago | parent
goda90 1 hour ago | parent
jasonvorhe 1 hour ago | parent
pwg 43 minutes ago | parent
lunar_rover 2 minutes ago | parent
senorrib 1 hour ago | parent
petterroea 1 hour ago | parent
flohofwoe 52 minutes ago | parent
goalieca 38 minutes ago | parent
In a way, applications regressed a lot with react native and electron. I get it’s easier to develop but the apps are very bloated and underperforming even on computers with 10-100x more power.
Neywiny 1 hour ago | parent
Also, pro tip, you can still just use it in browser. I hope that doesn't go away.
LoganDark 1 hour ago | parent
opengrass 1 hour ago | parent
fg137 53 minutes ago | parent
https://github.com/zed-industries/zed/discussions/17212
I don't know if we have a winner here.
smusamashah 1 hour ago | parent
swinglock 41 minutes ago | parent
LaurensBER 1 hour ago | parent
With the ram prices as crazy as they are. It's pretty frustrating to have to run multiple GB eating applications just to do some basic tasks (90% is read and write messages, in the case of Discord). I understand that other people might use the more advanced features (voice chat, etc) but these could be loaded on-demand.
It's a bit crazy to me that I can comfortable run an entire Linux stack (+ Podman, monitoring, alerting and multiple services) in 512 MB ram (with 40% free, just checked!). However my Windows PC needs 5.5GB just to show the desktop! Realistically it needs somewhere between 8GB and 16GB for some basic web browsing and even then it can feel slow if you have a few apps like Discord running in the background.
pasc1878 44 minutes ago | parent
You show this by all your other comments on memory. The reason apps take memory is Electron.
Plus I prefer apps that behave like OS native apps not the reduced GUI of web apps.
bemtevi 1 hour ago | parent
I don't know...there seems to be something unpleasant about all Electron apps.
cpursley 49 minutes ago | parent
bscphil 13 minutes ago | parent
Doohickey-d 23 minutes ago | parent
Most Rust GUI toolkits, at least in 2025, did not have that good accessibility or IME: https://www.boringcactus.com/2025/04/13/2025-survey-of-rust-...
Hopefully this has gotten better and the new discord client isn't worse in that regard.
robin_reala 4 minutes ago | parent
I haven’t tested it or written anything using GPUI, but I’d expect it to be considerably harder work, based on the maturity of the web stack in this area. My assumptions have definitely been proven wrong before though… Anyone from Discord working on accessibility want to chime in?
[2] https://github.com/zed-industries/zed/blob/main/crates/gpui/...
tapper 23 minutes ago | parent
tapper 16 minutes ago | parent
mococa 15 minutes ago | parent
azuanrb 13 minutes ago | parent
Raycast, originally a native macOS launcher, recently released v2 using a hybrid architecture. It’s not Electron, but it follows a similar approach to Spotify’s desktop app, using web technologies inside a native shell.
The memory usage is still pretty significant. It’s using around 350–450 MB at idle and can sometimes reach 1–2 GB depending on the workload. The upside is that they can now share most of their code across macOS and Windows and evolve beyond being just an app launcher.
It’s always been about trade-offs, and LLMs don’t fundamentally change that.
scosman 7 minutes ago | parent
GPUI is one example: some of the downsides of electron (UI is not native), but it solves memory and performance side, and shared codebase.
Just writing native apps because LLMs makes it cheaper is the other option. Shopify did this after years of react native.
jrmg 8 minutes ago | parent