3 ms·

Unless you are using a pretty crippled computer to work on, then yes, you may not need VSCode/Atom. Otherwise I don't see an issue here. everything is about ch

by equasar 10y ago

Unless you are using a pretty crippled computer to work on, then yes, you may not need VSCode/Atom. Otherwise I don't see an issue here. everything is about choice. These benchmarks on a modern i3/i5 processors and with 8GB of ram, which is almost the standard now, wont give those slow numbers published. also, I'm pretty sure VSCode at least have gained way more performance that you wouldn't notice these "lags".

aphextron 10y ago
>These benchmarks on a modern i3/i5 processors and with 8GB of ram, which is almost the standard now, wont give those slow numbers published. I don't think that's true at all. My personal experience using both VSCode and Atom on my i7-6700k/16GB work machine has mirrored these results. Files over 30-40k lines simply crash the program.
- equasar 10y ago
  Maybe sending those crash reports might help you to get them fixed, pretty sure next release (early April) would get fixed. Or if you use insiders build, could get fixed sooner.
- juandazapata 10y ago
  Me too. Tried Atom for 1 week and crashed about 4 times. I went back to vim (I once saw vim crash with a segfault in 10 years of usage).
juandazapata 10y ago
Add a Slack application with 5 organizations, a Chrome browser with 10 tabs opened, and you'll find yourself in a pretty curious situation.
- bobwaycott 10y ago
  I run Slack all day, signed into and switching among 4 accounts. Plus Apple's Messages. Plus chrome and safari, each with at least 6 windows open and dozens of tabs among them. And I then have at least 2 instances of VSCode open, each with dozens of tabs. I never experience the slightest perceptible speed or performance problem. This is on a late 2015 MBP with 16GB RAM. On my prior machine, with the same daily behavior, I still never experienced performance problems in VSCode. I used to use ST2 & ST3. Bought both. I just don't find a compelling case for it given the huge and active extension community for VSCode. Slack, however, frequently has performance problems. I also don't open files regularly that exceed 4-digit line counts.

by equasar 10y ago

aphextron 10y ago

>These benchmarks on a modern i3/i5 processors and with 8GB of ram, which is almost the standard now, wont give those slow numbers published. I don't think that's true at all. My personal experience using both VSCode and Atom on my i7-6700k/16GB work machine has mirrored these results. Files over 30-40k lines simply crash the program.

equasar 10y ago
Maybe sending those crash reports might help you to get them fixed, pretty sure next release (early April) would get fixed. Or if you use insiders build, could get fixed sooner.
juandazapata 10y ago
Me too. Tried Atom for 1 week and crashed about 4 times. I went back to vim (I once saw vim crash with a segfault in 10 years of usage).

juandazapata 10y ago

Add a Slack application with 5 organizations, a Chrome browser with 10 tabs opened, and you'll find yourself in a pretty curious situation.

bobwaycott 10y ago
I run Slack all day, signed into and switching among 4 accounts. Plus Apple's Messages. Plus chrome and safari, each with at least 6 windows open and dozens of tabs among them. And I then have at least 2 instances of VSCode open, each with dozens of tabs. I never experience the slightest perceptible speed or performance problem. This is on a late 2015 MBP with 16GB RAM. On my prior machine, with the same daily behavior, I still never experienced performance problems in VSCode. I used to use ST2 & ST3. Bought both. I just don't find a compelling case for it given the huge and active extension community for VSCode. Slack, however, frequently has performance problems. I also don't open files regularly that exceed 4-digit line counts.