Difference between revisions of "Editors and IDEs/vsCode"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
==vsCode!== | ==vsCode!== | ||
==="Code editing. Redefined."=== | ==="Code editing. Redefined."=== | ||
− | |||
− | |||
I consider this entry to be Microsoft's opinionated response to the wild success of [[Editors_and_IDEs/Atom | Atom]]. | I consider this entry to be Microsoft's opinionated response to the wild success of [[Editors_and_IDEs/Atom | Atom]]. | ||
Line 16: | Line 14: | ||
As far as I see it, there are only 2 possible problems that one could have with this editor: | As far as I see it, there are only 2 possible problems that one could have with this editor: | ||
− | + | ||
− | + | * There's a more purpose built editor for your use case | |
− | + | * You're concerned the Microsoft's collection of "telemetrics", I suggest you check out [[Editors and_IDEs/vsCodium|VsCodium]]! | |
− | + | ||
Full and Official documentation available at: https://code.visualstudio.com/ | Full and Official documentation available at: https://code.visualstudio.com/ |
Latest revision as of 16:13, 25 March 2021
vsCode!
"Code editing. Redefined."
I consider this entry to be Microsoft's opinionated response to the wild success of Atom.
They used the same basic software stack to make a very similar editor, and with a SLIGHTLY different result!
vsCode lacks the large file handling issues of Atom, and is less customizable, and with a slightly less robust plugin community...
The ability to edit a large file and scroll without stuttering however is enough to outweigh what I consider shortcomings.
For this reason, i switched to vsCode from Atom in 2019.
As far as I see it, there are only 2 possible problems that one could have with this editor:
- There's a more purpose built editor for your use case
- You're concerned the Microsoft's collection of "telemetrics", I suggest you check out VsCodium!
Full and Official documentation available at: https://code.visualstudio.com/