Moreover, to work on such a project, you will open each file in a new tab, leading to multiple VS Code instances running simultaneously, and eventually, your CPU usage will start to look like this. The Search Indexing and File Watcher scripts start eating up your memory. The problem starts here: the more files you have and the bigger your project, the more resources VS Code will start to consume. When you work on big projects with lots of files, the folder structure starts looking like this. So I decided to look into it, and I found out that the culprit was VS Code. They complained about this often, and after a while, I just couldn't ignore the issue. Some of my teammates started complaining about their systems slowing down when working on that project. So while we were working on a big old project, I observed something. I use to write a column of top VS Code Themes and Plugins every month in my monthly blog series "Ultra List" as well, but recently, I shifted back to Sublime Text. Up until just a few days ago, I was a VS Code lover like anyone else these days. Okay, this will be a really quick article.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |