Discord is ditching Electron and its new app uses less RAM

Discord is rebuilding its desktop and mobile clients in Rust using the GPUI framework, moving away from Electron and React Native to dramatically reduce RAM usage and improve performance. Commenters welcome the shift as part of a broader trend of using AI-assisted native rewrites to replace heavy web-tech wrappers, but raise concerns about lost modding flexibility, accessibility maturity, and dependence on opaque AI-generated code. The change also reignites debate over Electron’s trade-offs, the bloat of modern desktop apps, and whether tighter, native implementations can realistically stay maintainable at scale.

Memory use & performance

  • Many welcome the move away from Electron, citing Discord’s high RAM footprint (e.g., >1GB on Linux) as excessive for a chat app.
  • The Rust/GPUI prototype reportedly uses ~290MB RAM; some say that’s still high for messaging, others argue Discord is now a full social platform (voice, video, games, rich media) so complexity justifies more memory.
  • Some users note Electron bloat accretes over updates (leftover bundles), inflating disk usage. Others call exaggerated size claims (e.g. “10GB”) misinformation or jokes.

Electron vs native / cross‑platform trade‑offs

  • Critics: shipping a full browser engine per app is wasteful for RAM, disk, and security attack surface; Electron became a crutch so teams could avoid native work.
  • Defenders: Electron solves many “boring” problems (cross‑platform, accessibility, IME, RTL, packaging, tooling), and rebuilding that stack in Rust/GPUI risks re‑implementing a browser with fewer features and more bugs.
  • There’s debate over whether cross‑platform native UI with good UX is realistic versus “write once, test everywhere.”

Role of AI and “vibecoding”

  • Several comments claim such a rewrite would have been unrealistic a few years ago; LLMs now make large ports (JS→Rust, Electron→native) feasible.
  • Others worry that AI‑generated codebases are verbose, harder to understand, and erode institutional knowledge—future engineers may rely on models instead of deep comprehension.
  • Some suggest iterative AI‑assisted rewrites with tests and benchmarks, not one‑shot “revibes,” to retain architecture and maintainability.

GPUI choice & accessibility

  • Discord is using GPUI (the Rust GPU‑accelerated UI framework originally from a code editor).
  • Some praise GPUI (and higher‑level kits around it) as finally “complete enough” for serious products; others note fragmentation and limited upstream openness.
  • Accessibility is a major concern: GPUI historically lacked first‑class a11y; commenters point to integrations via AccessKit and third‑party crates but note these are still maturing and may lag platform‑native toolkits.
  • People worry that if the native client becomes mandatory, users of assistive tech could be locked out; browser access and web client retention are seen as important safeguards.

Modding, third‑party clients & policies

  • Several lament that moving off Electron will make modding (e.g., CSS tweaks, custom clients) harder; some expect determined reverse‑engineering and alternative clients anyway.
  • Discord’s ToS bans unofficial clients, and people report prior bans for detectable modifications; others advocate “hiding” clients or simply moving to alternatives.

Broader ecosystem & alternatives

  • Many hope other Electron-heavy apps (Slack, Teams, VS Code‑likes) follow with native or Rust ports.
  • Others prefer ditching Discord entirely in favor of open/self‑hosted solutions (Matrix, Discourse, Chatto, etc.), citing privacy, ads, and account‑verification practices.