4 ms·
I'm surprised that emacs users and some vim users too are switching to VSCode. Assuming I am not RAM constrained (I have "only" 6 but my system never lags- I ha
by fxfan 8y ago
I'm surprised that emacs users and some vim users too are switching to VSCode. Assuming I am not RAM constrained (I have "only" 6 but my system never lags- I have 0 chromium engines on my system), what is your workflow and what does VSCode do better?
- foldr 8y agoSensible defaults are a big part of it for me. Using VSCode means that I spend very little time configuring the editor, or setting up extensions.
- fxfan 8y agoWhy would you spend time doing anything? You just do it once and commit it to github? That's how my vimrc lives.
- foldr 8y agoDoes doing it once not take time? I usually get bored halfway through and switch to an editor that works properly out of the box. In fact, of course, doing it once is a pipe dream. Everything with vim and emacs 90% works, and you can spend infinite amounts of time chasing the other 10%.
- F-0X 8y agoAs far as Common Lisp goes, you could just install the Portacle distribution of emacs. This is essentially a fully-geared up CL IDE, including all the favourite emacs extensions for development (flycheck, company, paredit, magit, etc) and even SBCL and git! It provides a single user.el file for user-specific configuration, but as it stands it is an excellent "emacs with great defaults".
- ioddly 8y agoFor me it was TypeScript. I had terrible slowdowns in vim for whatever reason (was using a couple different plugins, and maybe things have improved since then), and VSCode is hands down the best TypeScript editor. I then found it to be a nicer experience for JS in general as well as C/C++. I still use vim often but since I'm not a vim power user, the vim emulation mode/plugin for any particular editor is generally good enough for me.