Atom is quite the heavyweight compared to VSC, especially once you load in a few plugins.
Atleast about a year back when I used it, Atom quickly filled up about 8GB of RAM for a moderately sized project in Go plus all necessary plugins.
VSC is fast but no lightweight either and hogs some resources.
It's not inherently a problem with Javascript, usually it's some framework like React being misused as usual inducing a lot of GC activity on top of unnecessary memory bloat.
I work in the public sector, you wouldn’t believe how many terrible programs I see each year. They are made in C++, C#, Swift, Java and so on, but you wouldn’t find me blaming WPF because someone didn’t know how to use it. :p
There are a lot of great electron apps, that frankly don’t have non-electron equals, so it obviously works. Yet it somehow always gets hit with these “well c++ could have done it better”.
Maybe it’s true, but if the biggest problem with electron is people using a framework wrong. Then what makes you think they’d do a better job in c++?
Atleast about a year back when I used it, Atom quickly filled up about 8GB of RAM for a moderately sized project in Go plus all necessary plugins.
VSC is fast but no lightweight either and hogs some resources.
It's not inherently a problem with Javascript, usually it's some framework like React being misused as usual inducing a lot of GC activity on top of unnecessary memory bloat.