4 ms·
Well, that's just the issue. I have no problem with Electron apps as an idea, but they're often coupled with extremely slow rendering. You can tell immediately.
by STRML 11y ago
Well, that's just the issue. I have no problem with Electron apps as an idea, but they're often coupled with extremely slow rendering. You can tell immediately.
For instance, in Slack, which is more or less an Electron app / browser in a box, I can easily get it down to <5 fps just by posting a snippet or going too far in scrollback. Resizing the window is beyond painful, etc., etc. It all seems unbelievably unnecessary - why should a chat program, literally text on a screen, perform like this on a top-of-the-line quad-core i7 system?
- Klathmon 11y agoHaving a problem with the performance is perfect criticism, but the commenter i was replying to was bashing it because of it's choice, not because of it's performance. He won't even try it before saying that. web rendering doesn't automatically make an app slow. And in my experience choosing a "common" platform like the web allows an app to run everywhere. I'm not suddenly going to be able to triple my development speed, so without the common platform that means that i'd only be able to support one major platform, or all platforms but with a small fraction of the development speed, and most likely many more bugs. And to be fair, saying slack is nothing more than "text on a screen" is really oversimplifying it. There are tons of formatting options, code highlighting, embedded HTML, embedded video and images, attachments, coloring, emojis, and more. It seems like a pretty obvious choice to go with a web rendering engine seeing as it supports almost all of that "natively".
- stephenr 11y agoPerformance, usability, conformance to platform standards, you name it, packaged web views are terrible for it.