3 ms·

And VSCode moves a step closer to being 'Emacs, now written in Javascript'

by NikkiA 7y ago

0xTJ 7y ago
I use VS Code as my main IDE for both business and pleasure, but I have to mistrust just how developer-friendly Microsoft has been. VS Code is a great, extendable, developer-friendly tool. WSL has made it so that it's less of a shame that I'm stuck using Windows for now. Even CMD has been getting updates that makes it behave more like a POSIX shell.
- heavenlyblue 7y ago
  Microsoft had always been developer-friendly. They just haven't been friendly much towards developers outside their ecosystem, as soon as they have monopolised the given ecosystem.
oaiey 7y ago
Without knowing too much about emacs (vi user.. just kidding), but I imagine the interface is either a proprietary C interface or a Unix Domain Socket with an Language Server behind it. Both do not scale up to the needs of today (Windows support, Remote Support, solving the n x m problem, ...).
pdpi 7y ago
Nothing of the sort. We can discuss how Emacs and VSCode compare to each other (and we can discuss the advantages and disadvantages of VSCode taking the electron approach until we're blue in the face), but VSCode is definitely not trying to compete with Emacs, rather aiming for a very different user base. However, this article isn't even about VS Code proper. It's about Debug Adapter Protocol. If DAP achieves the same adoption as LSP, this will be a huge move forward in developer tooling across all sorts of tech stacks and domains. In between LSP and DAP, just about any editor is capable of becoming a lightweight IDE for an enormous variety of languages, and this is a Good Thing for everybody.
zellyn 7y ago
As a long-time Emacs user, I think you're not totally wrong. The thing is, it's the idea of Emacs that's important; you could argue that Emacs itself is an antiquated and idiosyncratic implementation of that idea. I'm fine with parallel attempts at programmable editors; seems like a win.

And VSCode moves a step closer to being 'Emacs, now written in Javascript'

by NikkiA 7y ago

And VSCode moves a step closer to being 'Emacs, now written in Javascript'

0xTJ 7y ago

I use VS Code as my main IDE for both business and pleasure, but I have to mistrust just how developer-friendly Microsoft has been. VS Code is a great, extendable, developer-friendly tool. WSL has made it so that it's less of a shame that I'm stuck using Windows for now. Even CMD has been getting updates that makes it behave more like a POSIX shell.

heavenlyblue 7y ago
Microsoft had always been developer-friendly. They just haven't been friendly much towards developers outside their ecosystem, as soon as they have monopolised the given ecosystem.

oaiey 7y ago

Without knowing too much about emacs (vi user.. just kidding), but I imagine the interface is either a proprietary C interface or a Unix Domain Socket with an Language Server behind it. Both do not scale up to the needs of today (Windows support, Remote Support, solving the n x m problem, ...).

pdpi 7y ago

Nothing of the sort. We can discuss how Emacs and VSCode compare to each other (and we can discuss the advantages and disadvantages of VSCode taking the electron approach until we're blue in the face), but VSCode is definitely not trying to compete with Emacs, rather aiming for a very different user base. However, this article isn't even about VS Code proper. It's about Debug Adapter Protocol. If DAP achieves the same adoption as LSP, this will be a huge move forward in developer tooling across all sorts of tech stacks and domains. In between LSP and DAP, just about any editor is capable of becoming a lightweight IDE for an enormous variety of languages, and this is a Good Thing for everybody.

zellyn 7y ago

As a long-time Emacs user, I think you're not totally wrong. The thing is, it's the idea of Emacs that's important; you could argue that Emacs itself is an antiquated and idiosyncratic implementation of that idea. I'm fine with parallel attempts at programmable editors; seems like a win.