Sure, wasteful RAM and CPU is a big problem with Electron, but bigger problems not addressed in the article include:<p>- Total disregard for the user interface experience of the host operating system, as native UI toolkits are often not used<p>- Since native UI toolkits are not used, knowledge that the user already has about using their computer and how user interface elements should behave becomes useless every time they download a new Electron app with a different "design"<p>- Electron app developers are rarely qualified to design good usable UI elements from scratch and are often really bad at it<p>- Complete lack of accessibility integration - don't even bother trying to use an Electron app with a screen reader or other assistive tech<p>Yes, Electron helps you to rapidly prototype and release something faster, and it might even lower the barrier to app development, but it also encourages JFDI mentality and somehow the poor end-users get forgotten about.
I like that the author decided to take a different approach to thinking about electron, but his argument that everything is fine for him on his macbook that has 16gb of ram seems rather weak. Many users may have more economic laptops that have a realistic 4 - 8 gb of ram. If he were to try using a dev machine with specs more along those lines, I would be more willing to agree with him.