VS Code is a text editor / IDE. Compared to something like Notepad++, it’s super slow to open/load, its UI feels laggy at times, and it’s just overkill for opening a text file. Compared to specialized log viewers, it struggles with large files and is generally super slow.
But compared to “full” IDEs like IntelliJ, it’s marginal in coding features, lacking important analysis and testing support, plus integrations with ~everything.
If you find yourself in the middle, like many JS developers do, not actually needing the biggest IDE but also needing more than just a text editor, it’s a fine tool. As a Java Backend Dev, VS Code feels like a joke if applied to that, OTOH.
Honestly, vscode opens in a split second for me, faster than I can react and start typing. For all intents and purposes it is instantaneous. Granted my setup is extremely clean and I only have the barest extensions installed for my workflow. The performance is consistent in my Windows, macOS and Linux machines.
I can’t imagine it running slow at all (perhaps someone with hundreds or thousands of extensions would). The last two editors I could recall that took the whole of eternity in the time space continuum to load were Eclipse and Atom. And those were slowass right out of the gate with zero extensions or plugins.
People should use with whatever they feel comfortable with, but I personally don’t see the advantage. I used VSCode once for simple edits of something and it worked, but I couldn’t imagine really using it for a project due to the lack of… everything. The whole support of the JetBrains products from the smart autocompletion, pointing out errors in advance, to improving your code, is insane, and with VSCode, you don’t have that.
I also once had a small project with two people using PyCharm and one VSCode and the differences in the code style were insane. Of course that depends on the person, but it’s just much easier to obey all the style guidelines and write cleaner code with the former one.
To be fair, there’s a big difference.
VS Code is a text editor / IDE. Compared to something like Notepad++, it’s super slow to open/load, its UI feels laggy at times, and it’s just overkill for opening a text file. Compared to specialized log viewers, it struggles with large files and is generally super slow.
But compared to “full” IDEs like IntelliJ, it’s marginal in coding features, lacking important analysis and testing support, plus integrations with ~everything.
If you find yourself in the middle, like many JS developers do, not actually needing the biggest IDE but also needing more than just a text editor, it’s a fine tool. As a Java Backend Dev, VS Code feels like a joke if applied to that, OTOH.
Because it’s a webbrowser in disguise. The most complex and inperformant GUI rendering system in existence.
Oops. TY, corrected!
Honestly, vscode opens in a split second for me, faster than I can react and start typing. For all intents and purposes it is instantaneous. Granted my setup is extremely clean and I only have the barest extensions installed for my workflow. The performance is consistent in my Windows, macOS and Linux machines.
I can’t imagine it running slow at all (perhaps someone with hundreds or thousands of extensions would). The last two editors I could recall that took the whole of eternity in the time space continuum to load were Eclipse and Atom. And those were slowass right out of the gate with zero extensions or plugins.
People should use with whatever they feel comfortable with, but I personally don’t see the advantage. I used VSCode once for simple edits of something and it worked, but I couldn’t imagine really using it for a project due to the lack of… everything. The whole support of the JetBrains products from the smart autocompletion, pointing out errors in advance, to improving your code, is insane, and with VSCode, you don’t have that.
I also once had a small project with two people using PyCharm and one VSCode and the differences in the code style were insane. Of course that depends on the person, but it’s just much easier to obey all the style guidelines and write cleaner code with the former one.