Classic bait-and-switch with their M*N to M+N argument; totally looks like Embrace-Extend-Extinguish
Here’s the relevant snippet from the Pylance language server’s T&Cs
> INSTALLATION AND USE RIGHTS. a) General. You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. b) Third Party Components. The software may include third party components with separate legal notices or governed by other agreements, as may be described in the ThirdPartyNotices file(s) accompanying the software.
That they would forbid their holy language server implementation from integrating with other editors exposes the perfidy at the heart of their LSP advocacy.
If they want to keep the extension proprietary and charge for the language server, that’s fine! But allow people to use it with whichever editor instead of forbidding it through the license.
It’s wholly malicious to use a language server implementation to extend control to the editor landscape. This is exactly the kind of nonsense that got them in trouble in the 90s, in the first place.
Seems like Microsoft is back to pissing in the public pool.
So, they claim that much of what pylance does is mirrored by Pyright (which is open source)
I agree with you that it's pretty crap, and it leaves a bad taste in my mouth, but I'm willing to cut them some slack because of how great lsp is.
Seriously, the pushing of this makes up for a lot of nonsense, especially as its a standard which means that if it's successful, Microsoft will be mostly forced to abide by that standard within their products.
Here’s the relevant snippet from the Pylance language server’s T&Cs
> INSTALLATION AND USE RIGHTS. a) General. You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. b) Third Party Components. The software may include third party components with separate legal notices or governed by other agreements, as may be described in the ThirdPartyNotices file(s) accompanying the software.
Ref: https://github.com/microsoft/pylance-release/issues/4#issuec...
———
That they would forbid their holy language server implementation from integrating with other editors exposes the perfidy at the heart of their LSP advocacy.
If they want to keep the extension proprietary and charge for the language server, that’s fine! But allow people to use it with whichever editor instead of forbidding it through the license. It’s wholly malicious to use a language server implementation to extend control to the editor landscape. This is exactly the kind of nonsense that got them in trouble in the 90s, in the first place.
Seems like Microsoft is back to pissing in the public pool.