4 ms·
> VS Code users are generally pretty junior or solo. Once a developer gets serious they'll usually need to go to a full IDE If you mean exclusive "VS Code user
by SideburnsOfDoom 4y ago
> VS Code users are generally pretty junior or solo. Once a developer gets serious they'll usually need to go to a full IDE
If you mean exclusive "VS Code users" then maybe.
As an IDE user for one file type (in my case *.cs ) I still find VS code a very useful tool for any other file types. I can install linters and formatters for them, e.g. for yaml, json, xml, text etc. and VS code then makes a great editor, hits a good spot between "still fairly light and fast" and "has features".
An IDE focuses on one task. VS code complements it by being a "swiss army knife"
- usrusr 4y agoAfter Crockford's "js is scheme" claim, curly emacs was bound to eventually happen. If you come to VS code from e.g. IntelliJ, the UI is surprisingly opaque, considering its undoubtedly graphic nature. Not quite C-m M-c M-butterfly opaque, but not that far from it.
- SideburnsOfDoom 4y ago> If you come to VS code from e.g. IntelliJ, the UI is surprisingly opaque, considering its undoubtedly graphic nature You don't need to memorise all the things in VS Code, just know to open the "Command Pallete", and that's on the menu.
- fisf 4y agoThat works just about the same way in intellij.
- usrusr 4y agoIJ does have the "search everywhere" that can be used like the command palette, but it's still far from abandoning the idea of trying to make everything available in menu trees and the like. Plugins add cute pictures to the toolbar like it's 1999. VS:C is far more radical, there's The Palette and that's it.