72
Tech Talk: How Electron went Wayland-native, and what it means for your apps | Electron
(www.electronjs.org)
this post was submitted on 28 Mar 2026
72 points (98.6% liked)
Linux
13059 readers
549 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I hate Electron apps with a passion.
They are always so heavy and inefficient. I sometimes run complex video encoding/upscaling tasks in the background that push my computer to it's limits (for hours on end) and you can really get a feel for which applications are badly made. Electron apps always perform worse even if what they are doing is relatively simple.
And there are always weird edge cases with OS integration with Electron apps. Sometimes it's done well, other times not so much.
I use obsidian extensively, and I love it. It certainly does seem to use WAY more system resources than it should though, and I assume that electron is to blame. It's a shame they didn't base it on a different framework.
Perhaps someone who knows more about web development can explain what sort of upsides electron brings with it.
Programs run everywhere from the same codebase.
Well that's certainly a big plus point.