Re:I’m switching from VS Code to VS Codium
by bitwize on Sunday June 12, 2022 @11:21AM
(#31715168)
Who's to say we aren't productive with our chosen editors?
I find malarkey like autocomplete to be distracting, so I use Emacs with it turned off. Because Emacs can be programmed and extended as it is used, it is way more productive to me than any "fixed function" IDE -- including Visual Studio Code[0] I could not do my job nearly as effectively in Visual Studio Code or JetBrains as I do in Emacs.
There is a perspective dependence to what the "best tool for the job" is. You are most productive in JetBrains and that is fine, but that doesn't make your colleagues less productive in their choice of editor.
[0] To extend Visual Studio Code, you have to start a new Node TypeScript project that uses VSCode's cumbersome API, compile it, test it in an "Extension Host", bundle it in a .vsix and then, at long last, you can use it in your regular editor. It's clear that Visual Studio Code's designers did not want end users programming their editor, let alone programming and using it at the same time. As a VSCode end user, the happy path is to select from pre-made extensions in Microsoft's extension catalog.
I find malarkey like autocomplete to be distracting, so I use Emacs with it turned off. Because Emacs can be programmed and extended as it is used, it is way more productive to me than any "fixed function" IDE -- including Visual Studio Code[0] I could not do my job nearly as effectively in Visual Studio Code or JetBrains as I do in Emacs.
There is a perspective dependence to what the "best tool for the job" is. You are most productive in JetBrains and that is fine, but that doesn't make your colleagues less productive in their choice of editor.
[0] To extend Visual Studio Code, you have to start a new Node TypeScript project that uses VSCode's cumbersome API, compile it, test it in an "Extension Host", bundle it in a .vsix and then, at long last, you can use it in your regular editor. It's clear that Visual Studio Code's designers did not want end users programming their editor, let alone programming and using it at the same time. As a VSCode end user, the happy path is to select from pre-made extensions in Microsoft's extension catalog.