5 ms·

I spent 25 years using emacs before vscode (1997 to 2022-ish). I didn't go deep, I mostly just enjoyed the core parts of emacs + ccmode. I don't enjoy LISP but

by lysace 2y ago

I spent 25 years using emacs before vscode (1997 to 2022-ish). I didn't go deep, I mostly just enjoyed the core parts of emacs + ccmode. I don't enjoy LISP but I still enjoy emacs, if that makes any sense. MS made some very real and very usable innovations. Emacs hackers/maintainers would be wise to copy them, like I'm sure Microsoft copied things from emacs. It's a bit like the UI aspect of the browser wars. Everyone wins when good things are cloned and then iteratively improved upon.

datadrivenangel 2y ago
What are the ways that VScode is better than Emacs?
- lysace 2y ago
  I listed my favorites above. Generalizing it: Having smart people who really understand UX helps a lot with minimizing those months of pain before the payoff.
- baq 2y ago
  vscode does three things extremely well: defaults, defaults and defaults. The most important ‘you just need M-x do-whatever after installing the whatever-doer package’ is supported out of the box (no details on purpose, try running emacs or vim without any config and compare to a clean fresh install of vscode).
  - znpy 2y ago
    Re: defaults. Sometimes i wonder if it’s worth giving those new emacs distributions a shot. I’m thinking about spacemacs or doom emacs. They look cool but so far i’ve been okay with stock emacs.
    - qubitcoder 2y ago
      I used Spacemacs for years and recommend it to others. It was fantastic in the early days, but the stability seems to have diminished. I encountered more bugs over time that I'd have to troubleshoot and fix myself. I switched to Doom Emacs a couple of years ago. It's well-maintained with regular updates, fantastic language support, and lightning fast. The CLI tooling is also nice (i.e., you can run 'doom upgrade' to update everything, or 'doom doctor' if you encounter an issue). It's the closest equivalent to VS Code in terms of working out of the box. Not to mention the advantages of Emacs with Vim keybindings. There is a learning curve, but the GitHub documentation is excellent. Adding support for Ruby on Rails development, for example, is as simple as uncommenting '(ruby +rails +lsp)' line in the '~/.config/init.el' file, and then running 'doom sync'. There's a long list of supported languages and tooling [0]. [0] https://github.com/doomemacs/doomemacs/blob/master/static/init.example.el https://github.com/doomemacs/doomemacs/blob/master/static/in...

by lysace 2y ago

datadrivenangel 2y ago

What are the ways that VScode is better than Emacs?

lysace 2y ago
I listed my favorites above. Generalizing it: Having smart people who really understand UX helps a lot with minimizing those months of pain before the payoff.
baq 2y ago
vscode does three things extremely well: defaults, defaults and defaults. The most important ‘you just need M-x do-whatever after installing the whatever-doer package’ is supported out of the box (no details on purpose, try running emacs or vim without any config and compare to a clean fresh install of vscode).
- znpy 2y ago
  Re: defaults. Sometimes i wonder if it’s worth giving those new emacs distributions a shot. I’m thinking about spacemacs or doom emacs. They look cool but so far i’ve been okay with stock emacs.
  - qubitcoder 2y ago
    I used Spacemacs for years and recommend it to others. It was fantastic in the early days, but the stability seems to have diminished. I encountered more bugs over time that I'd have to troubleshoot and fix myself. I switched to Doom Emacs a couple of years ago. It's well-maintained with regular updates, fantastic language support, and lightning fast. The CLI tooling is also nice (i.e., you can run 'doom upgrade' to update everything, or 'doom doctor' if you encounter an issue). It's the closest equivalent to VS Code in terms of working out of the box. Not to mention the advantages of Emacs with Vim keybindings. There is a learning curve, but the GitHub documentation is excellent. Adding support for Ruby on Rails development, for example, is as simple as uncommenting '(ruby +rails +lsp)' line in the '~/.config/init.el' file, and then running 'doom sync'. There's a long list of supported languages and tooling [0]. [0] https://github.com/doomemacs/doomemacs/blob/master/static/init.example.el https://github.com/doomemacs/doomemacs/blob/master/static/in...