When the next paragraph says “the product underneath is Electron,” it is talking about the post-2014 wave of new code editors that built on Atom and then VS Cod

When the next paragraph says “the product underneath is Electron,” it is talking about the post-2014 wave of new code editors that built on Atom and then VS Code and then Cursor. JetBrains is the standing exception to that wave, not part of it. In that sense, JetBrains is not a hold-out, it's a progenitor. It was the first IDE development team to decide that it would rather require extra computing resources from you, then bother running a build script. Granted, Sun was so effective in their efforts to reduce the footprint of the Java VM, that it had dropped from the traditional two to four times overhead to only tens of percents more CPU and RAM resources, and their was no reason to beleive this wouldn't only improve, especially with coming hardware support for virtualization. In the end what we got was Electron using tenfold the RAM that a native application would require, and IDEs so bloated they make FPGA development environments lean in comparison.