3 ms·

This is a false dichotomy. My high-level functional programming etc etc is all there but I love emacs and (rather against my instincts) Visual Studio has som

This is a false dichotomy. My high-level functional programming etc etc is all there but I love emacs and (rather against my instincts) Visual Studio has some very nice features; for example not having to request a compile to get errors. This can be a huge timesaver. I therefore flip back and forwards between emacs and VS pretty freely. VS to get instant mistake-feedback and fix them, emacs to do most anything else. You can be a maven for both, but I don't think you can be a complete language expert for multiple languages. Then again, perhaps you don't have to be, just a solid grasp without knowing the dark corners is quite sufficient to get real work done. Edit: emacs has omnisharp which provides some instant feedback and some refactoring, but it's a lot better in VS.

dgb23 6y ago
VSCode is getting better w/o me doing anything, almost magically. I did three attempts to switch to emacs because I assume it would up my mechanics in the long term, but VSCode strikes a balance of being comfortable and powerful enough, and the community around it is very active.
- throwaway_pdp09 6y ago
  I promise you, emacs FTW in certain things which is why I persist with it (I'm a pragmatist not a masochist). VS certainly in others. They complement, but if I could have VS's features in emacs, I wouldn't leave it.
  - IggleSniggle 6y ago
    Just FYI I assumed you were taking about Visual Studio, not VSCode (a very different product), when you said VS. Every now and then I see emacs features that I wish existed in VSCode, and often I feel like VSCode extensions are reinventing the wheel but less well and more expensively...and yet, I’ve mostly given up and just use VSCode, because what it does right is make it relatively easy for anybody to write whatever feature they might want to exist, for the most part in whatever language with a small adapter to JavaScript, and package it as an extension.
    - throwaway_pdp09 6y ago
      Right, I'll check out the difference Visual Studio vs VSCode. Didn't know, thanks.
- ChickeNES 6y ago
  I actually just dumped VSCode and went back to Neovim+extensions. I grew tired of node processes running in the background chewing up CPU and RAM even when I had it minimized, not to mention general flakiness.

dgb23 6y ago

VSCode is getting better w/o me doing anything, almost magically. I did three attempts to switch to emacs because I assume it would up my mechanics in the long term, but VSCode strikes a balance of being comfortable and powerful enough, and the community around it is very active.

throwaway_pdp09 6y ago
I promise you, emacs FTW in certain things which is why I persist with it (I'm a pragmatist not a masochist). VS certainly in others. They complement, but if I could have VS's features in emacs, I wouldn't leave it.
- IggleSniggle 6y ago
  Just FYI I assumed you were taking about Visual Studio, not VSCode (a very different product), when you said VS. Every now and then I see emacs features that I wish existed in VSCode, and often I feel like VSCode extensions are reinventing the wheel but less well and more expensively...and yet, I’ve mostly given up and just use VSCode, because what it does right is make it relatively easy for anybody to write whatever feature they might want to exist, for the most part in whatever language with a small adapter to JavaScript, and package it as an extension.
  - throwaway_pdp09 6y ago
    Right, I'll check out the difference Visual Studio vs VSCode. Didn't know, thanks.
ChickeNES 6y ago
I actually just dumped VSCode and went back to Neovim+extensions. I grew tired of node processes running in the background chewing up CPU and RAM even when I had it minimized, not to mention general flakiness.