4 ms·

I presently use VS code at work as well, but not because it so nice, but rather that I can setup it from scratch to the tolerable state within 20 minutes includ

by _0w8t 5y ago

I presently use VS code at work as well, but not because it so nice, but rather that I can setup it from scratch to the tolerable state within 20 minutes including extension installation time and it works very similar on Linux/Mac/Windows (I need to work on all platforms and cross-platform functionality is a must). Plus it works on huge source tree like Chromium with fast file opening and whole tree search with almost no setup (VS Code hits some default limits on amount og Git modules, but that can be adjusted). I stopped using Emacs like 10 years ago after realising that if one needs over 1000 lines of init.el then I am not the target user of the editor. I tried to reduce that via using external packages, but that has not helped much. And for hobby projects I am happy with Geany on Linux.

bborud 5y ago
Do you use the syncing features? I sync to Github, so if I install VS Code on a new machine it takes a lot less than 20 minutes. That bit works great.
- zeppelin101 5y ago
  It takes a couple minutes, at most, if you sync settings.
- _0w8t 5y ago
  I have not bothered to use sync as I can setup VS code fast enough without it. Plus there are settings that require platform-specific adjustments. Maybe there are some ifs in the config that covers it, but I just see no point to spend time figure out it when I know I can spent 20 minutes max few times a year and do the setup from scratch.
b5n 5y ago
To each their own, but it doesn't take long to setup Emacs from scratch to the exact state I want. git clone myemacs mv myemacs ~/.emacs.d emacs
- _0w8t 5y ago
  The point is not to spend time writing init.el in the first place. I only need to setup few times per year and the time I spent writing my init file for Emacs is way bigger than I can save even in 100 years of using VS code. Some people enjoy hacking their configs, but for me the changes were due to Emacs defaults not to my taste. So I got no pleasure in writing the thing.
qubitcoder 5y ago
This is why I've been using Spacemacs as my primary editor for years now: cross-platform support, automatic language detection, package installation, well-designed key bindings, great documentation, etc. Not to mention significant productivity gains from packages such as magit (it's always fun when people see Git time machine in action--using the n/p keys to move backwards and forwards in time to see every change to a file, along with the commit message). And it works across all major OSes. Just copy your .spacemacs file to a new laptop, and wait for everything to install itself. To be fair, I use VS Code pretty regularly as well. But more of a nicer alternative to TextEdit/Gedit/etc. to capture notes as I work in Spacemacs (of course, there's also the helpful scratch buffer). [0] https://www.spacemacs.org https://www.spacemacs.org

by _0w8t 5y ago

bborud 5y ago

Do you use the syncing features? I sync to Github, so if I install VS Code on a new machine it takes a lot less than 20 minutes. That bit works great.

zeppelin101 5y ago
It takes a couple minutes, at most, if you sync settings.
_0w8t 5y ago
I have not bothered to use sync as I can setup VS code fast enough without it. Plus there are settings that require platform-specific adjustments. Maybe there are some ifs in the config that covers it, but I just see no point to spend time figure out it when I know I can spent 20 minutes max few times a year and do the setup from scratch.

b5n 5y ago

To each their own, but it doesn't take long to setup Emacs from scratch to the exact state I want. git clone myemacs mv myemacs ~/.emacs.d emacs

_0w8t 5y ago
The point is not to spend time writing init.el in the first place. I only need to setup few times per year and the time I spent writing my init file for Emacs is way bigger than I can save even in 100 years of using VS code. Some people enjoy hacking their configs, but for me the changes were due to Emacs defaults not to my taste. So I got no pleasure in writing the thing.

qubitcoder 5y ago

This is why I've been using Spacemacs as my primary editor for years now: cross-platform support, automatic language detection, package installation, well-designed key bindings, great documentation, etc. Not to mention significant productivity gains from packages such as magit (it's always fun when people see Git time machine in action--using the n/p keys to move backwards and forwards in time to see every change to a file, along with the commit message). And it works across all major OSes. Just copy your .spacemacs file to a new laptop, and wait for everything to install itself. To be fair, I use VS Code pretty regularly as well. But more of a nicer alternative to TextEdit/Gedit/etc. to capture notes as I work in Spacemacs (of course, there's also the helpful scratch buffer). [0] https://www.spacemacs.org https://www.spacemacs.org