4 ms·

> What can't you do with VSCode these days? Run it on a machine with less than 8GB of RAM.

CharlesW 6y ago
Microsoft recommends 1+ GB of free RAM, which seems reasonable based on the few times I've checked RAM usage out of curiosity.
throw_m239339 6y ago
Nah, I'm running a cheap N5000 (1.10 GHz) with 4 GB of RAM at home and VScode runs well. At the end of the day, it's the extensions that might slow the editor down as they greatly vary in quality. With only some Typescript/LESS/Node/Linting/Live Reload extensions, VSCode is sitting at 70 Mo right now. I think Microsoft did a great job with it. My machine can barely run Android Studio or Webstorm on the other hand, unless I turn off code inspection.
- raihansaputra 6y ago
  That's amazing. I've been trying to profile which extensions are causing my slowdowns but still not getting a satisfactory result. I think my ESLint/Vetur is re-checking all open files on every keystroke (not debounced) and it becomes slow after a few hours of the editor being open. But I can't really get it down to a specific extension.
  - jakear 6y ago
    Have you tried profiling the extension host?
    - raihansaputra 6y ago
      Thanks for the tip! Seems like Bracket Pair Colorizer 2 and Rainbow Indentation doesn't play nicely with the Vim extension. Bracket Pair Colorizer 1 is fine though, but I don't have a replacement yet for Rainbow Indentation.
- hevelvarik 6y ago
  Are you running a browser with multiple tabs, just boggles my mind how that works with 4gb. Are you using a funky light weight window manager. I truly wish to know how you manage it.
jjeaff 6y ago
You wouldn't have the development velocity of vs code without Electron. $50 of ram is a small price to pay for better software.
ldoughty 6y ago
seems very slim to me, I've used a fork of it on a Raspberry Pi without issues (Side note: recent VSCode release supposedly has ARM support now)
spiderfarmer 6y ago
Don't complain about things that already have obvious solutions. A lot of programmers think investing in hardware is stupid, because they think "if it was just coded more efficiently, I wouldn't have to". If my car can't pull a trailer that's too heavy, I can complain that the trailer is too heavy and spend way too much time hauling stuff. Or I can buy a car that's better suited for the job and do more work in one day. That's a stupid analogy of course, because a machine with 32Gb of RAM often costs less than what you make in a week. Stop complaining, just deal with it.

Microsoft recommends 1+ GB of free RAM, which seems reasonable based on the few times I've checked RAM usage out of curiosity.

throw_m239339 6y ago

Nah, I'm running a cheap N5000 (1.10 GHz) with 4 GB of RAM at home and VScode runs well. At the end of the day, it's the extensions that might slow the editor down as they greatly vary in quality. With only some Typescript/LESS/Node/Linting/Live Reload extensions, VSCode is sitting at 70 Mo right now. I think Microsoft did a great job with it. My machine can barely run Android Studio or Webstorm on the other hand, unless I turn off code inspection.

raihansaputra 6y ago
That's amazing. I've been trying to profile which extensions are causing my slowdowns but still not getting a satisfactory result. I think my ESLint/Vetur is re-checking all open files on every keystroke (not debounced) and it becomes slow after a few hours of the editor being open. But I can't really get it down to a specific extension.
- jakear 6y ago
  Have you tried profiling the extension host?
  - raihansaputra 6y ago
    Thanks for the tip! Seems like Bracket Pair Colorizer 2 and Rainbow Indentation doesn't play nicely with the Vim extension. Bracket Pair Colorizer 1 is fine though, but I don't have a replacement yet for Rainbow Indentation.
hevelvarik 6y ago
Are you running a browser with multiple tabs, just boggles my mind how that works with 4gb. Are you using a funky light weight window manager. I truly wish to know how you manage it.

jjeaff 6y ago

You wouldn't have the development velocity of vs code without Electron. $50 of ram is a small price to pay for better software.

ldoughty 6y ago

seems very slim to me, I've used a fork of it on a Raspberry Pi without issues (Side note: recent VSCode release supposedly has ARM support now)

spiderfarmer 6y ago

Don't complain about things that already have obvious solutions. A lot of programmers think investing in hardware is stupid, because they think "if it was just coded more efficiently, I wouldn't have to". If my car can't pull a trailer that's too heavy, I can complain that the trailer is too heavy and spend way too much time hauling stuff. Or I can buy a car that's better suited for the job and do more work in one day. That's a stupid analogy of course, because a machine with 32Gb of RAM often costs less than what you make in a week. Stop complaining, just deal with it.