4 ms·

At this point I am 100% sure, VS code will become a IDE like Visual Studio.

by minionslave 8y ago

azhenley 8y ago
Is that bad? As long as it remains fast and easy to use, I am happy!
mikece 8y ago
If they ever add a visual editor that could be true. Still tons of thing Visual Studio does that VS Code doesn't.
- Kiro 8y ago
  Like what? Never used Visual Studio.
  - azhenley 8y ago
    A lot of debugging and profiling features.
2bitencryption 8y ago
I think the key is that it has the potential to be a great platform. The text-editing "fundamentals" are covered by the Monaco engine. The rest is covered by extensions. Out of the box, it's not much more than a glorified Notepad. Add some extensions and suddenly I'm stepping through my Rust breakpoints and inspecting values.
- parvenu74 8y ago
  The language server protocol (LSP) is a massive leap forward. And unlike the Microsoft of Ballmer, LSP is an open standard that any editor designer can implement.
  - mr_overalls 8y ago
    Is there any reason to use LSP, rather than simple JSON messages passed between the front-end and back-end? That's the approach that Xi uses. https://github.com/xi-editor/xi-editor https://github.com/xi-editor/xi-editor
    - chmln 8y ago
      Because LSP is a widely used protocol for language tooling that's not coupled to any particular editor. I'm surprised xi didn't just add an LSP client to leverage the existing ecosystem. The benefits of in-house language server implementations seem marginal at best.
    - dragonwriter 8y ago
      > Is there any reason to use LSP, rather than simple JSON messages passed between the front-end and back-end Yes, there's a reason to use a documented open standard supported by multiple servers and clients that passes JSON back and forth rather than an ad hoc, client specific mechanism that also passes JSON back and forth. In fact, the reason is exactly the problem LSP addresses, labeled as “The Matrix” at https://langserver.org https://langserver.org In short, a problem with N+M cost is better than N×M when both N and M are >2.
    - pkaye 8y ago
      LSP also uses JSON messages.
    - WorldMaker 8y ago
      Most LSP work is just simple JSON messages passed with HTTP-like headers for Content-Type and Content-Length, presumably to future proof it against other payload formats. https://microsoft.github.io/language-server-protocol/specification https://microsoft.github.io/language-server-protocol/specifi...
    - shawnz 8y ago
      What makes you say Xi's protocol is simpler just because the messages are encoded with JSON?
bunderbunder 8y ago
For many languages it's pretty much there, if you install the right extensions. Sometimes, yeah, excessively so. But then you uninstall that extension and it's a nice, reasonably lightweight editor again.
PurpleRamen 8y ago
I thing it's already more an IDE than a plain editor. There is not even a normal file-explorer anymore, just an workspace-explorer. Using VS Code for regular editor-stuff is kinda painful IMHO.

At this point I am 100% sure, VS code will become a IDE like Visual Studio.

azhenley 8y ago

Is that bad? As long as it remains fast and easy to use, I am happy!

mikece 8y ago

If they ever add a visual editor that could be true. Still tons of thing Visual Studio does that VS Code doesn't.

Kiro 8y ago
Like what? Never used Visual Studio.
- azhenley 8y ago
  A lot of debugging and profiling features.

2bitencryption 8y ago

I think the key is that it has the potential to be a great platform. The text-editing "fundamentals" are covered by the Monaco engine. The rest is covered by extensions. Out of the box, it's not much more than a glorified Notepad. Add some extensions and suddenly I'm stepping through my Rust breakpoints and inspecting values.

parvenu74 8y ago
The language server protocol (LSP) is a massive leap forward. And unlike the Microsoft of Ballmer, LSP is an open standard that any editor designer can implement.
- mr_overalls 8y ago
  Is there any reason to use LSP, rather than simple JSON messages passed between the front-end and back-end? That's the approach that Xi uses. https://github.com/xi-editor/xi-editor https://github.com/xi-editor/xi-editor
  - chmln 8y ago
    Because LSP is a widely used protocol for language tooling that's not coupled to any particular editor. I'm surprised xi didn't just add an LSP client to leverage the existing ecosystem. The benefits of in-house language server implementations seem marginal at best.
  - dragonwriter 8y ago
    > Is there any reason to use LSP, rather than simple JSON messages passed between the front-end and back-end Yes, there's a reason to use a documented open standard supported by multiple servers and clients that passes JSON back and forth rather than an ad hoc, client specific mechanism that also passes JSON back and forth. In fact, the reason is exactly the problem LSP addresses, labeled as “The Matrix” at https://langserver.org https://langserver.org In short, a problem with N+M cost is better than N×M when both N and M are >2.
  - pkaye 8y ago
    LSP also uses JSON messages.
  - WorldMaker 8y ago
    Most LSP work is just simple JSON messages passed with HTTP-like headers for Content-Type and Content-Length, presumably to future proof it against other payload formats. https://microsoft.github.io/language-server-protocol/specification https://microsoft.github.io/language-server-protocol/specifi...
  - shawnz 8y ago
    What makes you say Xi's protocol is simpler just because the messages are encoded with JSON?

bunderbunder 8y ago

For many languages it's pretty much there, if you install the right extensions. Sometimes, yeah, excessively so. But then you uninstall that extension and it's a nice, reasonably lightweight editor again.

PurpleRamen 8y ago

I thing it's already more an IDE than a plain editor. There is not even a normal file-explorer anymore, just an workspace-explorer. Using VS Code for regular editor-stuff is kinda painful IMHO.