Who knows about memory, but I use modern hardware so not really a concern. Id rather software optimize for responsiveness than minimizing memory use. Computers are only getting cheaper over time, aggressively deflating in real terms
I can see how being more memory constrained might flip the priorities
I don't know what your definition of "modern hardware" is, but if a 32GB machine isn't enough to edit text files and run a glorified IRC without occasionally having to restart everything to reclaim memory, then yes, it really is a concern.
Re: the IntelliJ comparison: to me, IntelliJ feels qualitatively slower on average than VSCode, but VSCode routinely just stops doing anything at all and I have to restart it.
I hear this a lot, and I don't think it's outright false, but it's a bit like saying a supertanker is slower than a tug.
The capabilities are just so far apart that it's not a good comparison, IMO.
I'm an IntelliJ fan (and customer) so I'll state that for bias, but the sheer volume of things IntelliJ _CAN_ do compared to VSCode I think is just mind boggling. It might be slower, but I think to compare that aspect while not looking at why is not quite useful.
Where is the slowness?
The post is about UI being in native for performance reasons, yet most of the processing/heavy logic of an IDE already is, or in a separate thread, even if the UI is in Electron.
At which point you're just discussing the performance gap between Canvas rendering and native graphics, which to a large extent disappears with WebGPU.
Performance differences aren’t that meaningful at the margins. You tend to give up a lot of velocity when you eschew browser based rendering.
JetBrains is far slower than both
Hardly reducing any gap.
If you really want to eek out that marginal extra performance vs writing directly in JS. The truth is that the perception gap between web apps and native apps only shrinks over time, so that perceived performance matters less and less
Easy enough to disprove those that say browser based apps are inherently slow. Modern JS is significantly more optimized and faster than most other loosely typed runtimes, e.g python.
WebGPU will just close the gap further.
Anyway you can write highly optimized native code and deploy to browser via WASM anyway. No reason at all to deal with OS quirks. WASM compilation will get better and better over time