6 ms·

> Vim vs. Emacs is a sideshow at best. Until you need to ssh into a server and edit something.

58028641 6y ago
VS Code supports editing files over ssh. https://code.visualstudio.com/docs/remote/remote-overview https://code.visualstudio.com/docs/remote/remote-overview
- jackosdev 6y ago
  Yeah but you have to install 100+mb into a .vsserver folder to get it to work
  - not_knuth 6y ago
    sshfs?
    - sigjuice 6y ago
      Unfortunately, sshfs doesn't work on modern macOS.
      - deleted 6y ago
        [deleted]
      - prurigro 6y ago
        I just tested and it works for me, I'm fully up to date too.
        sigjuice 6y ago
        That is great! I thought Big Sur had deprecated kernel extensions which would prevent osxfuse and sshfs from working.
- deleted 6y ago
  [deleted]
BeetleB 6y ago
It's funny you mention that. https://www.murilopereira.com/how-to-open-a-file-in-emacs/ https://www.murilopereira.com/how-to-open-a-file-in-emacs/ The summary is that the author tried to open a remote file and Emacs froze for several seconds. He dived deep into finding out why that was and how to fix it, pointing out how great Emacs's introspection is that one can find solutions to problems like these. And then two thirds of the way into his essay, he has this: > More recently, I’ve been very put off by the performance and stability (or lack thereof) of building large scale software via Tramp. This has been sufficient to have me looking out again. On a whim, I installed VSCode for the first time and tried its “remote development” capabilities and holy smokes are they good. Getting up and running was trivial and the performance was great. Saving files was snappy and LSP worked out of the box. What a different experience from my carefully-put-together, half-working, slow Emacs setup. And then later: > Improve Tramp performance to match the experience of using terminal Emacs via SSH, or VSCode’s Remote Development.
- years3500 6y ago
  Well for what it's worth, here is something about VS Code LSP and embrace-extend-extinguish. https://news.ycombinator.com/item?id=25719338 https://news.ycombinator.com/item?id=25719338
  - BeetleB 6y ago
    This isn't about LSP but specifically pylance. Let's not confuse the issue. (Incidentally, I don't even use lsp on Emacs, although I may give it a try).
    - years3500 6y ago
      I think the thing is that pylance is a python LSP. And it's proprietary. So they embraced python LSP, extends it so that the additions are proprietary. And pylance might become the defacto python LSP. Typical EEE. Python is hugely popular, it's everywhere - so even if one hates it, might end up having to use it. Also the remote extensions are proprietary [1]. This has been discussed on HN before. [1] https://github.com/VSCodium/vscodium/issues/240 https://github.com/VSCodium/vscodium/issues/240
based8 6y ago
This always comes up. How can we still not edit a remote file via ssh using whatever you want!?!

VS Code supports editing files over ssh. https://code.visualstudio.com/docs/remote/remote-overview https://code.visualstudio.com/docs/remote/remote-overview

jackosdev 6y ago
Yeah but you have to install 100+mb into a .vsserver folder to get it to work
- not_knuth 6y ago
  sshfs?
  - sigjuice 6y ago
    Unfortunately, sshfs doesn't work on modern macOS.
    - deleted 6y ago
      [deleted]
    - prurigro 6y ago
      I just tested and it works for me, I'm fully up to date too.
      - sigjuice 6y ago
        That is great! I thought Big Sur had deprecated kernel extensions which would prevent osxfuse and sshfs from working.
deleted 6y ago
[deleted]

BeetleB 6y ago

It's funny you mention that. https://www.murilopereira.com/how-to-open-a-file-in-emacs/ https://www.murilopereira.com/how-to-open-a-file-in-emacs/ The summary is that the author tried to open a remote file and Emacs froze for several seconds. He dived deep into finding out why that was and how to fix it, pointing out how great Emacs's introspection is that one can find solutions to problems like these. And then two thirds of the way into his essay, he has this: > More recently, I’ve been very put off by the performance and stability (or lack thereof) of building large scale software via Tramp. This has been sufficient to have me looking out again. On a whim, I installed VSCode for the first time and tried its “remote development” capabilities and holy smokes are they good. Getting up and running was trivial and the performance was great. Saving files was snappy and LSP worked out of the box. What a different experience from my carefully-put-together, half-working, slow Emacs setup. And then later: > Improve Tramp performance to match the experience of using terminal Emacs via SSH, or VSCode’s Remote Development.

years3500 6y ago
Well for what it's worth, here is something about VS Code LSP and embrace-extend-extinguish. https://news.ycombinator.com/item?id=25719338 https://news.ycombinator.com/item?id=25719338
- BeetleB 6y ago
  This isn't about LSP but specifically pylance. Let's not confuse the issue. (Incidentally, I don't even use lsp on Emacs, although I may give it a try).
  - years3500 6y ago
    I think the thing is that pylance is a python LSP. And it's proprietary. So they embraced python LSP, extends it so that the additions are proprietary. And pylance might become the defacto python LSP. Typical EEE. Python is hugely popular, it's everywhere - so even if one hates it, might end up having to use it. Also the remote extensions are proprietary [1]. This has been discussed on HN before. [1] https://github.com/VSCodium/vscodium/issues/240 https://github.com/VSCodium/vscodium/issues/240

based8 6y ago

This always comes up. How can we still not edit a remote file via ssh using whatever you want!?!