Nah electron is an excellent technology, v8 is a remarkable engine. Maybe something like tauri will unseat it eventually but the ability to spin up a new product in relatively short order is good for everyone. Ram and disk usage are higher than they would be with a native app but velocity is unparalleled
The problem is chromium. It’s more efficient and usable to just create a new dedicated firefox profile (which will start in a fully separated instance), and create starter scripts and desktop entries for that.
Imo velocity and user experience aren’t mutually exclusive, as a developer I can respond to user requests way faster with web technologies.
As a consumer vscode is a perfect example of why the ecosystem has value, are there other products that fill the same roles? Absolutely, but if you were around for the transition from bloodshed, codeblocks, eclipse and the like to sublime and vscode and other more modern editors you should remember how gamechanging the positive feedback loop of velocity achieved for the dev community in the form of user experience.
A modern text editor with language servers running absolutely will take up 1GB+, I know I can easily get neovim to go past that with typescript projects.
I suspect most of the resource usage is LSP plugins, so equivalently configured neovim should be about the same, really. If you use VSCode as a plain text editor, it does not use that much RAM.
With 0 extensions it absolutely doesn’t take 1GB and the more extensions you add it resembles more an IDE than a text editor, so the 1GB is completely justified. In fact, I have tons of extensions and mine takes around 300MB, I have like 5 instances open for work reasons (several remote connections) running on a VDI that gives me like 4 GB of RAM, and I can open excel, teams, and all the other company bullshit, alongside a browser with 20 tabs open. So no, it doesn’t take 1GB per instance.
Nah electron is an excellent technology, v8 is a remarkable engine. Maybe something like tauri will unseat it eventually but the ability to spin up a new product in relatively short order is good for everyone. Ram and disk usage are higher than they would be with a native app but velocity is unparalleled
The problem is chromium. It’s more efficient and usable to just create a new dedicated firefox profile (which will start in a fully separated instance), and create starter scripts and desktop entries for that.
It’s sad that you prioritize “velocity” over user experience.
Imo velocity and user experience aren’t mutually exclusive, as a developer I can respond to user requests way faster with web technologies.
As a consumer vscode is a perfect example of why the ecosystem has value, are there other products that fill the same roles? Absolutely, but if you were around for the transition from bloodshed, codeblocks, eclipse and the like to sublime and vscode and other more modern editors you should remember how gamechanging the positive feedback loop of velocity achieved for the dev community in the form of user experience.
VSCode being essentially a text editor is a perfect example of software that should not use 1GB+ of RAM
A modern text editor with language servers running absolutely will take up 1GB+, I know I can easily get neovim to go past that with typescript projects.
Me, a casual: “wadderthefuckareyouguysarguingabout?”
I suspect most of the resource usage is LSP plugins, so equivalently configured neovim should be about the same, really. If you use VSCode as a plain text editor, it does not use that much RAM.
With 0 extensions it absolutely doesn’t take 1GB and the more extensions you add it resembles more an IDE than a text editor, so the 1GB is completely justified. In fact, I have tons of extensions and mine takes around 300MB, I have like 5 instances open for work reasons (several remote connections) running on a VDI that gives me like 4 GB of RAM, and I can open excel, teams, and all the other company bullshit, alongside a browser with 20 tabs open. So no, it doesn’t take 1GB per instance.
For most users software is not a religious question.