5 ms·

I switched from vscode to (doom) emacs. I don't know how it is now, but the vi-like key bindings of vscode were pretty bad at the time.

by forty 5y ago

ogogmad 5y ago
It takes a while for the time spent learning emacs/vi to amortise itself. You need to learn the key bindings, the ad hoc scripting language, and the substantial API. And throughout it all, there's the constant temptation to switch to something easier like vscode. I tried learning to use Org-mode as a Markdown replacement over Doom Emacs. At some point, I switched back to vscode+Markdown and it felt like a breeze. I'm not a SWE, so the payoff would've probably taken too long to happen. I also tried using the Maxima mode for Emacs as an interactive CAS. The only thing I got was Latex-formatted output and the same Emacs-like key bindings that you get in any terminal emulator. No auto-suggestion/Intellisense to help you navigate and avoid learning the API, so I wasn't overly impressed.
- forty 5y ago
  I have been using vi like key bindings for the past 15 years, so learning to do differently would be a significant investment I'm not willing to make, even moreso that the benefits would not be clear ;) But yes, I'm 100% convinced that it's not for everyone, and depends a lot of the quality of the integration/mode of your specific use case.
dangerbird2 5y ago
I hate to admit I'm in that camp. Used emacs because it has great support for editing over ssh. When vscode came out with remote connections for ssh and wsl, I switched over. Emacs is a great operating system-I mean editor, but it's pretty hard to extend it to have the feature set of newer editors while maintaining reasonable performance.
RealStickman_ 5y ago
Vim bindings are pretty good if you use the nvim plugin in vs code. It's not emulating (n)vim, you need to have the actual nvim installed and it will use that to provide the keyvindings. I also switched from vs code to doom emacs though, just because I wanted to.
- easygenes 5y ago
  I use code folding and find that abysmally broken with the normal vim mode extension in vs code. Is it any better with nvim?

I switched from vscode to (doom) emacs. I don't know how it is now, but the vi-like key bindings of vscode were pretty bad at the time.

by forty 5y ago

I switched from vscode to (doom) emacs. I don't know how it is now, but the vi-like key bindings of vscode were pretty bad at the time.

ogogmad 5y ago

It takes a while for the time spent learning emacs/vi to amortise itself. You need to learn the key bindings, the ad hoc scripting language, and the substantial API. And throughout it all, there's the constant temptation to switch to something easier like vscode. I tried learning to use Org-mode as a Markdown replacement over Doom Emacs. At some point, I switched back to vscode+Markdown and it felt like a breeze. I'm not a SWE, so the payoff would've probably taken too long to happen. I also tried using the Maxima mode for Emacs as an interactive CAS. The only thing I got was Latex-formatted output and the same Emacs-like key bindings that you get in any terminal emulator. No auto-suggestion/Intellisense to help you navigate and avoid learning the API, so I wasn't overly impressed.

forty 5y ago
I have been using vi like key bindings for the past 15 years, so learning to do differently would be a significant investment I'm not willing to make, even moreso that the benefits would not be clear ;) But yes, I'm 100% convinced that it's not for everyone, and depends a lot of the quality of the integration/mode of your specific use case.

dangerbird2 5y ago

I hate to admit I'm in that camp. Used emacs because it has great support for editing over ssh. When vscode came out with remote connections for ssh and wsl, I switched over. Emacs is a great operating system-I mean editor, but it's pretty hard to extend it to have the feature set of newer editors while maintaining reasonable performance.

RealStickman_ 5y ago

Vim bindings are pretty good if you use the nvim plugin in vs code. It's not emulating (n)vim, you need to have the actual nvim installed and it will use that to provide the keyvindings. I also switched from vs code to doom emacs though, just because I wanted to.

easygenes 5y ago
I use code folding and find that abysmally broken with the normal vim mode extension in vs code. Is it any better with nvim?