5 ms·

You can do all that and more in vscode as well... you just have to "learn to master and config" it with your own plugins in JS. It's not that hard.

by qppo 6y ago

umvi 6y ago
I tend to let other people "master and config" VSCode and then I just go download their extensions. IMO that's the beauty of VSCode - critical mass
- sedev 6y ago
  That's also available with emacs, though, it has its own extension ecosystem that's about as easy to access as VSCode's.
  - vopi 6y ago
    I don't think its as easy imo. vscode auto recommends extensions if you open a new file type and from what I remember (been a number of years since I installed a package in emacs), the extension "browser"/"market" was not as user friendly (in terms of raw info about the extension and in discoverability).
  - voxl 6y ago
    Yeah no, emacs package system is a giant mess, it's only "easy" if you've already drunk the emacs kool aid. Sorry I just really hate emacs.
thom 6y ago
Have you found that other extension authors have this in mind? Most extensions don't seem to be built with hooks in mind so you're kinda stuck with either the existing extension or rolling your own. There also aren't very good primitives for most use cases because of this. I assume VSCode will get there though.
- qppo 6y ago
  VSCode extensions are driven through "commands" that are exposed through the package.json of the plugin (which can be parsed by other plugins if you wanted) and issuable through another plugin, or using a task (this is kind of annoying though and not a first class use of tasks).
mercer 6y ago
I use VSCode for my day to day coding, so I have nothing against it, but explain to me how I can 'do' Magit and the like in VSCode...?
- ashtonian2 6y ago
  Literally anything you can do in emcas there is an extension for or at least one in dev. Vscode will outgrow emcas given its critics mass and momentum.
  - akho 6y ago
    “Critics mass” of whom? VS Code is very disappointing, given the hype. Can you give an example of something in the VS Code ecosystem that can impress an Emacs user enough to switch, beyond chrome? Chrome will always attract crowds, of course.
  - indymike 6y ago
    The question is will it grow in the right direction? Org-mode, magit and a pure terminal interface (can run on remotes through an SSH sesion) are still missing. Still love the ergonomics of vs code.
    - bubblesorting 6y ago
      VS Code runs on remote hosts through SSH, containers, or WSL: https://code.visualstudio.com/docs/remote/remote-overview https://code.visualstudio.com/docs/remote/remote-overview Kinda like a parallel universe swank/slime.
      - indymike 6y ago
        Yes... and has the same limitations of roundtripping files in any other IDE.
        bananaquant 6y ago
r-zip 6y ago
VSCode isn't as flexible at all though. You can't even create a keybinding that executes multiple commands (macro). There aren't hooks. You can't just write a function in a file and execute it. There isn't the same level of introspection. In a lot of ways, VSCode is more convenient, but its extensibility doesn't come close to matching Emacs'.

You can do all that and more in vscode as well... you just have to "learn to master and config" it with your own plugins in JS. It's not that hard.

by qppo 6y ago

You can do all that and more in vscode as well... you just have to "learn to master and config" it with your own plugins in JS. It's not that hard.

umvi 6y ago

I tend to let other people "master and config" VSCode and then I just go download their extensions. IMO that's the beauty of VSCode - critical mass

sedev 6y ago
That's also available with emacs, though, it has its own extension ecosystem that's about as easy to access as VSCode's.
- vopi 6y ago
  I don't think its as easy imo. vscode auto recommends extensions if you open a new file type and from what I remember (been a number of years since I installed a package in emacs), the extension "browser"/"market" was not as user friendly (in terms of raw info about the extension and in discoverability).
- voxl 6y ago
  Yeah no, emacs package system is a giant mess, it's only "easy" if you've already drunk the emacs kool aid. Sorry I just really hate emacs.

thom 6y ago

Have you found that other extension authors have this in mind? Most extensions don't seem to be built with hooks in mind so you're kinda stuck with either the existing extension or rolling your own. There also aren't very good primitives for most use cases because of this. I assume VSCode will get there though.

qppo 6y ago
VSCode extensions are driven through "commands" that are exposed through the package.json of the plugin (which can be parsed by other plugins if you wanted) and issuable through another plugin, or using a task (this is kind of annoying though and not a first class use of tasks).

mercer 6y ago

I use VSCode for my day to day coding, so I have nothing against it, but explain to me how I can 'do' Magit and the like in VSCode...?

ashtonian2 6y ago
Literally anything you can do in emcas there is an extension for or at least one in dev. Vscode will outgrow emcas given its critics mass and momentum.
- akho 6y ago
  “Critics mass” of whom? VS Code is very disappointing, given the hype. Can you give an example of something in the VS Code ecosystem that can impress an Emacs user enough to switch, beyond chrome? Chrome will always attract crowds, of course.
- indymike 6y ago
  The question is will it grow in the right direction? Org-mode, magit and a pure terminal interface (can run on remotes through an SSH sesion) are still missing. Still love the ergonomics of vs code.
  - bubblesorting 6y ago
    VS Code runs on remote hosts through SSH, containers, or WSL: https://code.visualstudio.com/docs/remote/remote-overview https://code.visualstudio.com/docs/remote/remote-overview Kinda like a parallel universe swank/slime.
    - indymike 6y ago
      Yes... and has the same limitations of roundtripping files in any other IDE.
      - bananaquant 6y ago

r-zip 6y ago

VSCode isn't as flexible at all though. You can't even create a keybinding that executes multiple commands (macro). There aren't hooks. You can't just write a function in a file and execute it. There isn't the same level of introspection. In a lot of ways, VSCode is more convenient, but its extensibility doesn't come close to matching Emacs'.