Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VSCode January 2019 (version 1.31) released

code.visualstudio.com

Post reply on HN
Print view View original

11–20 of 41 posts

Re: VSCode January 2019 (version 1.31) released

#11

Post by parvenu74 »

2bitencryption wrote: post #7
minionslave wrote: post #2

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

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.

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.

Re: VSCode January 2019 (version 1.31) released

#13

Post by mr_overalls »

parvenu74 wrote: post #11
2bitencryption wrote: post #7

Earlier quoted context omitted.

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.

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.

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

Re: VSCode January 2019 (version 1.31) released

#14

Post by fermienrico »

Can someone recommend a good tutorial on getting started with VSCode? I downloaded it and it feels overwhelming to develop C/C++ code compared to Sublime Text. ST has simple build system (just path to compiler) and it runs out of the box. With VSCode, there are extensions and .json files for configuration and it is all extremely complex and overwhelming.

Re: VSCode January 2019 (version 1.31) released

#15

Post by WorldMaker »

fermienrico wrote: post #14

Can someone recommend a good tutorial on getting started with VSCode? I downloaded it and it feels overwhelming to develop C/C++ code compared to Sublime Text. ST has simple build system (just path to compiler) and it runs out of the box. With VSCode, there are extensions and .json files for configuration and it is all extremely complex and overwhelming.

One place to start is that the official docs do have some per-language guides. The C++ guide:

https://code.visualstudio.com/docs/languages/cpp

Re: VSCode January 2019 (version 1.31) released

#16

Post by mpartel »

mikece wrote: post #6

Not reloading when adding an extension is a long-overdue feature, in my opinion. What were the technical reasons for needed to reload?

It's easier to write correct code when you know certain state changes always entail a full reload. Extension installs are rare enough and VSCode reloads quick enough that the tradeoff seems sensible.

This change introduces a new "extensions changed" event that extension points must (correctly) implement, so the cost is more code i.e. more opportunity for bugs. The essential question is of course, how much more, and I have no answer to that.

Re: VSCode January 2019 (version 1.31) released

#18

Post by WorldMaker »

mr_overalls wrote: post #13
parvenu74 wrote: post #11

Earlier quoted context omitted.

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.

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

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/specifi...

Re: VSCode January 2019 (version 1.31) released

#19

Post by shawnz »

mr_overalls wrote: post #13
parvenu74 wrote: post #11

Earlier quoted context omitted.

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.

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

What makes you say Xi's protocol is simpler just because the messages are encoded with JSON?
Post reply on HN