It’s still from a UI/UX perspective needlessly complicated. I wish they would make things a bit more obvious.
I find that the ability to search through all available actions with Ctrl+shift+P makes things very discoverable.
VSCode January 2019 (version 1.31) released
21–30 of 41 posts
Re: VSCode January 2019 (version 1.31) released
#22Have they fixed keyboard shortcuts to actually match OS X shortcut semantics? Eg cmd-f/g not focusing the search field? Or using the system search text properly? (Cmd e iirc - I thought about it so that memory is now gone :) )
Re: VSCode January 2019 (version 1.31) released
#23Re: VSCode January 2019 (version 1.31) released
#24I tried VS Code early on and decided I'd give it a serious shot when I could modify the color scheme without having to go through a whole page of notes, download and install something like 3 other programs and practically learn a whole new language.
Is that possible yet? In other words, is there an actual GUI for configuring color, or at least a config file that's not some cryptic format for a program I've never used?
Re: VSCode January 2019 (version 1.31) released
#25I tried VS Code early on and decided I'd give it a serious shot when I could modify the color scheme without having to go through a whole page of notes, download and install something like 3 other programs and practically learn a whole new language. Is that possible yet? In other words, is there an actual GUI for configuring color, or at least a config file that's not some cryptic format for a program I've never used…
I know I'm probably exaggerating quite a bit, but I literally couldn't figure out how to do it after wasting a fair bit of time and gave up.
I was raised in the era of "programmer editors" like Brief and Multi-edit (the latter of which I still use) and those were always extremely easy to configure and enhance without having to use a bunch of external tools.
Re: VSCode January 2019 (version 1.31) released
#26Re: VSCode January 2019 (version 1.31) released
#27Earlier 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
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.
Re: VSCode January 2019 (version 1.31) released
#28Earlier 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
> 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
In short, a problem with N+M cost is better than N×M when both N and M are >2.
Re: VSCode January 2019 (version 1.31) released
#29Earlier 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
LSP also uses JSON messages.
Re: VSCode January 2019 (version 1.31) released
#30Fun fact: this is the first stable version that can start even without internet (LAN) connection on latest Windows 10 update 1809. (Mentioned as first Notable fix [0], fixed by updating Electron to v3.)