3 ms·

Are you aware that VS Code is the driving force behind key standards such as the Language Server Protocol https://langserver.org/ https://langserver.org/ and De

Are you aware that VS Code is the driving force behind key standards such as the Language Server Protocol https://langserver.org/ https://langserver.org/ and Debug Adapter Protocol https://microsoft.github.io/debug-adapter-protocol/ https://microsoft.github.io/debug-adapter-protocol/? These standards have revolutionised IDE language support in the last few years meaning I can now run my code on a remote machine and connect to it using VS Code or any other LSP compatible IDE. I write a language server for a niche scripting language, and Microsoft's specs mean that I wrote support for VS Code and now Sublime text, Emacs, Vim, Atom, etc all just have support too. You can, right now, run VS Code on your Linux server, and another copy on your Windows desktop, and just use SSH to connect them seamlessly: https://code.visualstudio.com/docs/remote/ssh https://code.visualstudio.com/docs/remote/ssh Sure, this currently uses a Microsoft server to set up the connection, but I'm sure the moment they lock that down someone would fork the extension and provide an alternative.

stephc_int13 6y ago
VS Code is a formidable piece of engineering, I've used it for years and have mostly been impressed by the quality. The problem is that I sense a potential bait & switch tactic. I don't want to live in world where the norm is that everything in on the so-called "cloud". I want full ownership of my files and my tools.
- donmcronald 6y ago
  It will be EXACTLY like MS Office IMO. They won’t drop the standalone version outright, but at some point all the new, compelling features will only go into the cloud version. We’ll pay for everything. We’ll be renting our syntax highlighting if they think people will tolerate it. I think we’ll pay per CPU cycle, but the cost will be based on feature tiers. IE: CPU cycles * features = mega profit.
  - Dayshine 6y ago
    > We’ll be renting our syntax highlighting if they think people will tolerate it Again, go look at the LSP. There are already alternative IDEs that are compatible with VS Code extensions. You can use the exact same community written syntax highlighting extension in a different IDE without touching any Microsoft code at all...
thejosh 6y ago
And yet things like the .NET Core debugger which is touted around has an closed license. (Microsoft .NET Core Debugger licensing and Microsoft Visual Studio Code) - https://github.com/OmniSharp/omnisharp-vscode/wiki/Microsoft-.NET-Core-Debugger-licensing-and-Microsoft-Visual-Studio-Code https://github.com/OmniSharp/omnisharp-vscode/wiki/Microsoft... Microsoft mainly does things that helps lock people into their systems. Why do you need to connect to their server at all? It's all about control.
- Dayshine 6y ago
  What does a specific extension's license have to do with VS Code? The only argument I can see is that they should be going back to all their old corporate contracts and renegotiating them to allow open source, but that's hardly a problem with VS Code. I can release an extension with whatever license I want.

stephc_int13 6y ago

VS Code is a formidable piece of engineering, I've used it for years and have mostly been impressed by the quality. The problem is that I sense a potential bait & switch tactic. I don't want to live in world where the norm is that everything in on the so-called "cloud". I want full ownership of my files and my tools.

donmcronald 6y ago
It will be EXACTLY like MS Office IMO. They won’t drop the standalone version outright, but at some point all the new, compelling features will only go into the cloud version. We’ll pay for everything. We’ll be renting our syntax highlighting if they think people will tolerate it. I think we’ll pay per CPU cycle, but the cost will be based on feature tiers. IE: CPU cycles * features = mega profit.
- Dayshine 6y ago
  > We’ll be renting our syntax highlighting if they think people will tolerate it Again, go look at the LSP. There are already alternative IDEs that are compatible with VS Code extensions. You can use the exact same community written syntax highlighting extension in a different IDE without touching any Microsoft code at all...

thejosh 6y ago

And yet things like the .NET Core debugger which is touted around has an closed license. (Microsoft .NET Core Debugger licensing and Microsoft Visual Studio Code) - https://github.com/OmniSharp/omnisharp-vscode/wiki/Microsoft-.NET-Core-Debugger-licensing-and-Microsoft-Visual-Studio-Code https://github.com/OmniSharp/omnisharp-vscode/wiki/Microsoft... Microsoft mainly does things that helps lock people into their systems. Why do you need to connect to their server at all? It's all about control.

Dayshine 6y ago
What does a specific extension's license have to do with VS Code? The only argument I can see is that they should be going back to all their old corporate contracts and renegotiating them to allow open source, but that's hardly a problem with VS Code. I can release an extension with whatever license I want.