Every Windows 11 app should kill Electron, and Discord just showed why

Electron-based desktop apps are under fire as Discord prepares a new Windows client written in Rust with the GPUI toolkit, which early demos suggest loads much faster and uses dramatically less RAM than its Electron predecessor. Commenters debate whether Electron’s original trade-off—single codebase, web tooling, and easy cross‑platform support in exchange for heavy resource use—still makes sense now that tools like Rust, Tauri, Avalonia, and LLM-assisted coding lower the cost of native or non‑browser UIs. Accessibility, IME support, and the maturity of alternative GUI frameworks remain open concerns, but many hope this signals a broader shift away from bloated web-wrapped desktop software.

Electron’s Value Proposition and Criticism

  • Many note Electron was attractive in the 2010s: one codebase, web skills, and Chrome’s broad API surface (webcam, media, etc.) across Windows/macOS/Linux.
  • Critics argue it always prioritized developer convenience and org structure (one team, fewer specialists) over user experience and efficiency.
  • Some defend Electron as “good for its time” like jQuery; others insist it was never a good solution and only survived because businesses didn’t fund native teams.
  • There’s frustration that Electron apps routinely consume hundreds of MB to multiple GB of RAM for relatively simple workloads.

Discord’s New Rust/GPUI Client

  • The new client is praised as a proof point that native-ish stacks can dramatically cut RAM and startup time.
  • Skeptics say the comparison may be premature: the app isn’t fully released or feature-complete, and any complex client embedding rich media will eventually face browser-engine-like needs.
  • Some suggest the gains might also reflect “less bloat so far,” not only the stack.

Cross‑Platform vs Native Toolkits

  • Thread revisits older cross-platform options (Qt, wxWidgets, Java, etc.) and notes they were viable but demanded more packaging and platform expertise.
  • Opinions split on whether to use a single cross-platform UI (Qt, Avalonia, GPUI, Dear ImGui, Slint, Tauri) vs thin native UIs sharing Rust or other core logic.
  • Several argue modern package managers (Cargo, vcpkg, CI) and LLMs make native or non-web cross-platform stacks much more feasible.

Accessibility and IME

  • Electron/web is praised for relatively strong, consistent accessibility and IME behavior “out of the box.”
  • Concern: many Rust GUI libraries still lag on accessibility and IME, especially for East Asian input; GPUI relies on AccessKit and may require more work.
  • Disabled users emphasize that accessibility is not what causes bloat; poor engineering and misuse of web APIs do.

Performance, UX, and User Empathy

  • Numerous complaints about sluggish, memory-heavy desktop environments (Windows in particular) and slow Electron apps vs older snappy native software.
  • Some developers accept Electron’s overhead as a reasonable trade-off; others call this laziness and urge taking on more “cognitive load” so users can reclaim hardware.
  • There is hope that Discord’s move and LLM-assisted development will trigger a broader return to fast, native-feeling desktop apps.