3 ms·
That sweet spot has nothing to do with compilation or Docker, and everything with the rise of Electron. Before, an app was built with native UI libraries, runni
by jorvi 9y ago
That sweet spot has nothing to do with compilation or Docker, and everything with the rise of Electron. Before, an app was built with native UI libraries, running on Python with core elements in C++ for speed. After, a simple app (like Slack or WhatsApp desktop) will eat 300-500mb, use 1-10% CPU and chew through your battery alive.
- leonroy 9y agoYeah it's pretty shocking how much CPU and memory Electron apps use. Used to be Java chat apps and IDEs (Eclipse, IntelliJ) were considered slow and bloated. They're practically fleet footed compared to the new breed of web apps. As much as I love Slack, Visual Studio Code and Atom my maxed out MacBook Pro is at 50-100% CPU and paging into swap with all three open. If I send a few GIFs in Slack - temps hit 99C (never 100 for some reason) and my laptop sounds like a mini hovercraft. It's a little disheartening and really has me missing those big old Mac Pros which were silent no matter the task. JavaScript and the resulting apps are certainly enjoyable to code and use but damn does something need to change in terms of resource utilization.
- musha68k 9y agoHey there, sorry even without using any Electron apps I still have performance issues which in my case have 99% to do with building applications within the bounds of "microservice" architectures. That said Electron apps sure eat up lots of (mostly single core) resources too, which ultimately amounts to a bad UX.