The "[surprising] little memory they use" is huge for what they do.
Edit: Yes, I think Electron/nodejs are "bloated" too if I look in node_modules - but once I stopped worrying about that I got over the whole "bloated" perception.
it wasnt slow scrolling up the conversation to see what someone said 10 minutes ago. try scrolling up a teams conversation to find a recent message.
roughly 750MB RAM...
I'm running all this stuff on a beefy desktop - I don't really care if it takes 200MB RAM to open a file as VC Code has lots of features I really like.
People used to edit code on a 1 MIPS 8MB 32BIT DEC VAX 11/780.
With 30 people doing the same, concurrently.
> I'm running all this stuff on a beefy desktop - I don't really care if it takes 200MB RAM to open a file as VC Code has lots of features I really like.
I have a bunch of machines. From ARM boards, ARM-based gadgets, Intel-based ultra-light laptop to a beefy Intel-based desktop.
If a tool runs a text editor editing a small file in 3/4 GB RAM, what will it do if the technology is used to develop some actually demanding things?
Edit: I've worked with people in my career who complained about 'bloat' in C (vs assember), C++ (vs C), Unix, Emacs (vs vi), Java (vs C++)
Complaining about the latest round of tools being bloated is just what a subset of the developer community does at any moment in time (and this is not necessarily a bad thing).
> I've worked with people in my career who complained about 'bloat' in C (vs assember), C++ (vs C), Unix, Emacs (vs vi), Java (vs C++)
That's a big hyperbole.