Discord is ditching Electron and its new app uses less RAM
theverge.com489 points by archb 2 days ago
489 points by archb 2 days ago
I had trouble reading more than the opening volley of the article due to popups. Am a Discord user, and rust application programmer: What GUI framework are they using? EGUI? GPUI? Something custom?
GPUI from comments? I meant to try GPUI, but backed off after an announcement pending its maintenance would be in question (?) a few months ago, and Zed broadly ending up being a false messiah, for my uses. (Not on the tier of JetBrains IDEs, a bug with a long thread they closed which (still I believe?) causes it to open cached versions of files, then clobber edits made since the cache, e.g. by other programs. I.e. the sort of bug which renders software too dangerous to use. I will not switch to a GUI framework from a group that ignores bugs of that severity reported by many people)
They use GPUI. Says so on X.
" (And it's not Tauri, it's GPUI, so good guess everyone.) "
Which I believe GPUI is the same framework that Zed (the editor)[0] is using
[0]: http://zed.dev/
The fact they're using gpui is... Bad. Is someone trying to make it integrate with native accessibility frameworks? If not (and if they force the native app on us) this transition is going to lock out a ton of people who use assistive technologies.
Yes, see: https://github.com/longbridge/gpui-kit. I've been following these rust UI toolkits and things like accessibility have consistently been missing. This is the first time I've seen a UI library that appears complete enough to build a real product with.
Yeah, that's what worries me. Pretty much every Rust UI library I've seen which isn't wxdragon/Relm/GTK lacks accessibility. And most of them don't even have the primitives for it (given that most of them are abandoned).
This response doesn't make sense?
GP you asked if there is accessibility P response: yes, here You then respond that worries you and dismiss the proof?
> This response doesn't make sense?
Apologies. I was noting that the lack of accessibility worried me (well, and weird accessibility breakage too).