I recently learned about the difference between VsCode and VsCodium. Long story short, VsCode binaries are distributed under a non-open-source license by Microsoft, even though they are built mostly from source code that is under MIT. VsCodium leaves the binaries under MIT and disables telemetry by default.
Given that Coq-community is committed to free and open source software, should we perhaps resolve to always recommend VsCodium over VsCode for use with VsCoq? Since VsCoq is already in the free, non-Microsoft VSX marketplace, the only reason to use VsCode+VsCoq is seemingly for using them together with other proprietary extensions.
I don't know if I would go as far as recommending VsCodium over VsCode especially for beginners. However I think it would be useful for people who care about this sort of thing to know VsCodium can be used instead. Since @Théo Zimmermann is knowledgeable about free and open source software, perhaps he can add more.
Personally for me, it doesn't matter much. But I am not a representative user.
I don't have an opinion on the matter.
some more recent background here: https://twitter.com/migueldeicaza/status/1537175065380495367
Truly disappointing that Microsoft would subvert an active open source project by ramming in a proprietary extension to continue to lockdown .NET. An unaccetable abuse of power from the stewards of the platform, and a betrayal of the community. https://github.com/omnisharp/omnisharp-vscode/issues/5276 https://twitter.com/migueldeicaza/status/1537175065380495367/photo/1
- Miguel de Icaza (@migueldeicaza)this was about a VsCode extension related to C#, but it shows where the wind is blowing, in some sense
Maybe I am unaware of the bigger context here. But is C# not Microsoft's project to begin with? If they implement a closed source LSP server, so what?
The compiler of C# started off as a closed source project, then mono came a long with open-source cross platform support and Microsoft bought it and then open-sourced much of the C# infrastructure.
But I don't see how this is relevant to Microsoft owning Github, VSCode etc.
Microsoft owns the VsCode Marketplace, and can shut it down anytime, or throw apps out, etc. Seems reasonable to funnel people towards an alternative where that doesn't happen.
I don't think we should recommend one over the other, simply name both options (well maybe put VSCodium in the front). More important IMHO is that we make sure VSCoq always works on VSCodium - initially (before VSX) using VSCoq in VSCodium was a bit rough, but now it is fine.
OK, I think we can then ask @Maxime Dénès how he feels about naming clearly both VsCode+marketplace and VsCodium+VSX in the VsCoq README (I'd be willing to submit a PR)
My first reaction would be I'd like to keep clear that VsCoq is a VsCode extension, because that's what most people are looking for (they typically don't know about VsCodium). Definitely ok with adding some text about VsCoq also supporting VsCodium (and making it true, of course). Even ok with some text explaining the differences between VsCode and VsCodium if not too controversial.
Karl Palmskog said:
Microsoft owns the VsCode Marketplace, and can shut it down anytime, or throw apps out, etc. Seems reasonable to funnel people towards an alternative where that doesn't happen.
I must confess I'm very ignorant on this. What measures are taken on the open-vsx side to prevent the Eclipse Foundation from being able to do the same?
The vendor neutral argument of the approach seemed more obvious to me.
I just tested VsCodium+VSX+VsCoq and it works fine. I'm fine with the "vendor neutral" approach.
for any piece of infrastructure, there are measures that can be taken by the owner, but it seems clear that the respective interests/incentives of Microsoft vs. Eclipse Foundation are somewhat different.
https://github.com/coq-community/vscoq/pull/296
@Maxime Dénès any chance for a review of the vendor-neutral-VsCodium-in-README PR?
Last updated: Jun 06 2023 at 23:01 UTC