“Visual Studio Code is one of the best code editors in this moment.”
I agree and have been using it since 2018. However, in that time, it has gotten more bloated and slower. Every month it seems yet another new feature is crammed into it (yet a feature request I follow has been languishing for five years now). I worry at some point it will be like current editions of Visual Studio that need almost the absolute latest CPU’s and a pile of memory to perform adequately. I have heard there is a forked lite version that uses less system resources and may try it at some point.
I hear you. However, vscode isn’t the main guilty in my opinion. The problems often are generated by the extensions, build not very well! I usually keep the number of extensions low to reduce this problem. Or try to detect which extension creates slowdowns!
Yes, extensions can be a massive contributor to resource usage. As I am primarily doing Node.js development, I have few extensions. In fact, I recently removed "Bracket Pair Colorizer 2", which had been a resource hog at one point until it was fixed, due to the functionality now being built-in to Code.
I have wonder how the version that comes out a year from now will compare in performance to this months version. As I mentioned, I recall how Visual Studio 2013 was slower than Visual Studio 2010 which itself was slower than Visual Studio 2008, 2005, 2003, etc. Visual Studio 2017 took forever to start up on hardware that ran 2013 adequately. Pretty much like iOS releases that force you to get new hardware every three years just to keep things running with reasonable speed.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
“Visual Studio Code is one of the best code editors in this moment.”
I agree and have been using it since 2018. However, in that time, it has gotten more bloated and slower. Every month it seems yet another new feature is crammed into it (yet a feature request I follow has been languishing for five years now). I worry at some point it will be like current editions of Visual Studio that need almost the absolute latest CPU’s and a pile of memory to perform adequately. I have heard there is a forked lite version that uses less system resources and may try it at some point.
I hear you. However, vscode isn’t the main guilty in my opinion. The problems often are generated by the extensions, build not very well! I usually keep the number of extensions low to reduce this problem. Or try to detect which extension creates slowdowns!
Yes, extensions can be a massive contributor to resource usage. As I am primarily doing Node.js development, I have few extensions. In fact, I recently removed "Bracket Pair Colorizer 2", which had been a resource hog at one point until it was fixed, due to the functionality now being built-in to Code.
I have wonder how the version that comes out a year from now will compare in performance to this months version. As I mentioned, I recall how Visual Studio 2013 was slower than Visual Studio 2010 which itself was slower than Visual Studio 2008, 2005, 2003, etc. Visual Studio 2017 took forever to start up on hardware that ran 2013 adequately. Pretty much like iOS releases that force you to get new hardware every three years just to keep things running with reasonable speed.