Live data from Hacker News

Microsoft discloses plans to turn parts of VS Code C# extension to closed source

github.com

31–40 of 42 posts

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#31
post #2

So, is this the Extend part now? Embrace is over? (I don't understand each of the terms of the slogan enough) Side note, I am guessing this means that Vim, Emacs etc using LSP don't get C# intellisense anymore?

As far as I know Emacs never used LSP for C# development, because OmniSharp doesn't use LSP. I doubt we'll get better IntelliSense from this move, but OmniSharp stays available to Emacs and so does its IntelliSense.

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#32

Language Server Protocol looks web-based. I'm extremely confused what it has to do with an IDE restricted to one machine.

My understanding is that VSCode uses it regardless of whether it's running locally or remotely. It's just an abstraction layer that happens to use web protocols for IPC instead of something local-only.

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#33
This nice feeling to be proved right a short time after being down voted by some in previous threads because they were sure that complaining about EEE with Microsoft was just being stuck in the past and that they have changed...

But now, you can see the usual embrace, extend and extinguish in action. They manage to get a lot of dev to use vscode saying that you don't have to worry as it is open source. Then they made extensions a need. Then they manage to have Gitlab and GitHub give up on alternatives like atom to get a monopoly on code editor. And now the fun could begin!

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#34

Earlier quoted context omitted.

Nothing that exists today is moving behind a closed-source model. Omnisharp will continue to be open and maintained but it won't be the default anymore.

ecosystem defaults was: open, like ruby, golang or rust ecosystem defaults now: closed, proprietary to ensure the programming language is only useful if you are a paying customer of Visual Studio. See the problem? More at https://isdotnetopen.com/

> is only useful if you are a paying customer of Visual Studio

I don’t see how that’s true since it’s going into VS Code, the free product.

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#35

Earlier quoted context omitted.

They have full right to do this. They are still scumbags for doing it. Nobody should be terribly surprised when a giant corporation behaves like a scumbag; it's a fundamental feature of such organizations. We as individuals have the responsibility of shunning them when they do this.

I'm curious, why are they scumbags? Aren't they free to decide how their time and effort is used? Do they have some inherent obligation to work for you for free(which is what open source is)? If you develop some piece of software, and use the open core model, I wouldn't consider you a scumbag.

You speak of them as if they were a person. Microsoft is not a person, so they indeed do not have the same rights as people do. Specifically, they can be called what they are with a far lower threshold than people, especially with the reputation they have accumulated over the decades.

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#37

Earlier quoted context omitted.

I'm curious, why are they scumbags? Aren't they free to decide how their time and effort is used? Do they have some inherent obligation to work for you for free(which is what open source is)? If you develop some piece of software, and use the open core model, I wouldn't consider you a scumbag.

You speak of them as if they were a person. Microsoft is not a person, so they indeed do not have the same rights as people do. Specifically, they can be called what they are with a far lower threshold than people, especially with the reputation they have accumulated over the decades.

I'm not totally familiar with their past actions, but you specifically called the fact that pylance is not open source (while the "pyright" core is) a "scumbag move", which is what I am arguing is unfair.

So I'm having trouble figuring out your position: is Microsoft a scumbag for not open sourcing pylance or not?

FWIW, I was, until recently, a daily user of pyright, and it's, by a million miles, the best LSP for python out there. The maintainer of pyright also contributes a LOT towards pushing forward the static typing ecosystem in python. In fact, the most recent PEP in Python static typing was initiated, drafted, and first implemented, by the maintainer of pyright[0].

Microsoft also has hired Guido Van Rossum to work on Python full time.

So I think calling Microsoft scumbags about an aspect of how they engage with the Python ecosystem is not only unfair, but totally misleading.

[0] https://peps.python.org/pep-0681/

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#38
post #36

The comments on this thread did't age well at all... They aren't going closed source and updated the thread to reflect so. Tldr; they are bringing closed source tools to the open source crowd.

There's not much of a practical difference between turning an open-source tool closed-source, and creating a closed-source replacement for an open-source tool and then letting the latter wither and die. In either case, the open-source one quickly becomes unusably outdated without a dedicated community fork effort.

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#39

Earlier quoted context omitted.

You speak of them as if they were a person. Microsoft is not a person, so they indeed do not have the same rights as people do. Specifically, they can be called what they are with a far lower threshold than people, especially with the reputation they have accumulated over the decades.

I'm not totally familiar with their past actions, but you specifically called the fact that pylance is not open source (while the "pyright" core is) a "scumbag move", which is what I am arguing is unfair. So I'm having trouble figuring out your position: is Microsoft a scumbag for not open sourcing pylance or not? FWIW, I was, until recently, a daily user of pyright, and it's, by a million miles, the best LSP for pyt…

You again talk about individuals and individual behavior and then switch seamlessly into talking about Microsoft. Even worse, you insinuate that dislike of Microsoft behavior is equal to dislike of individual Microsoft-adjacent peoples’ behavior.

No. These things are not the same and they should never be equated.

Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source

#40

Earlier quoted context omitted.

I'm not totally familiar with their past actions, but you specifically called the fact that pylance is not open source (while the "pyright" core is) a "scumbag move", which is what I am arguing is unfair. So I'm having trouble figuring out your position: is Microsoft a scumbag for not open sourcing pylance or not? FWIW, I was, until recently, a daily user of pyright, and it's, by a million miles, the best LSP for pyt…

You again talk about individuals and individual behavior and then switch seamlessly into talking about Microsoft. Even worse, you insinuate that dislike of Microsoft behavior is equal to dislike of individual Microsoft-adjacent peoples’ behavior. No. These things are not the same and they should never be equated.

I talked about the maintainer of Pyright (Eric Taut), and I talked about Guido Van Rossum. Both are currently salaried employees as Microsoft. The work they are doing is unambiguously enabled by the salaries that Microsoft pays them. They are not "Microsoft-adjacent", they are employed by Microsoft.

If one wants to evaluate Microsoft's moral standing with regards to their participation in the Python ecosystem, one must take into account the work done on the Python ecosystem by Microsoft's salaried employees, in their working hours, no?

Post reply on HN