News for hackers. Stuff that matters.

A comment on Microsoft Refuses to Open Source VSCode Python Language Server. Parent comment

Re:Microsoft Refuses to Open Source VSCode Python Language S... by petr_tik on Sunday January 10, 2021 @04:26PM (#25720083)
> by forbidding the use of their LSPs in other editors

How can they prevent my, let’s say vim, client from connecting to a closed-source server if they both speak the same protocol?

[ Parent | on HN ]
Re:Microsoft Refuses to Open Source VSCode Python Language S... by jlgaddis on Sunday January 10, 2021 @07:02PM (#25721984)
As pritambaral mentioned, they can make some minor changes to the server that are just enough to cause the client to no longer work.

This isn't exactly unheard of when it comes to Microsoft. I mean, you don't have to go far to find an example of them doing exactly that -- there's prime example [0] right here in this thread!

(Alsa known as "extend"; see also "Active Directory")

--

[0]: https://news.ycombinator.com/item?id=25719294

[ Parent | on HN ]
Re:Microsoft Refuses to Open Source VSCode Python Language S... by pritambaral on Sunday January 10, 2021 @04:45PM (#25720290)
One way would be to make the closed-source server speak mostly-but-not-quite-the-same protocol.
[ Parent | on HN ]
Re:Microsoft Refuses to Open Source VSCode Python Language S... by petr_tik on Monday January 11, 2021 @05:17PM (#25738232)
Other servers like clangd have documented extensions, but I see your point. I’m glad the protocol is discussed and developed in the open - I think it’s really helped the IDE story in other editors.
[ Parent | on HN ]