It's time for a rebirth of Atom, then! Except it's "owned" by Microsoft as well.
Oh, well... let's revive LightTable, then :)
The best Parts of Visual Studio Code are proprietary
191–200 of 277 posts
Re: The best Parts of Visual Studio Code are proprietary
#192Of course it is. VSCode is attractive to people who should be using Emacs, but were too afraid to try it. But unfortunately what you get is not Emacs, it's a Microsoft product and if you think they made it because of "love" then you are incredibly naïve.
Re: The best Parts of Visual Studio Code are proprietary
#193Earlier quoted context omitted.
> Yes and no. The complaint is that some widely used extensions are proprietary. If these extensions require MS servers, then they have every reason to be. Even if they don't, there's nothing wrong with a company holding back some stuff they consider strategic, they're not obligated to release them. that is kinda debatable, considering that those are extensions to an LGPL-licensed core (Blink, the rendering engine us…
The LGPL parts here are dynamically linked, which is exactly what the LGPL was supposed to let you do.
they definitely aren't. no libchromiumcontent.so to be seen anywhere.
$ ls /opt/visual-studio-code/**/*.so
/opt/visual-studio-code/libEGL.so
/opt/visual-studio-code/libffmpeg.so
/opt/visual-studio-code/libGLESv2.so
/opt/visual-studio-code/swiftshader/libEGL.so
/opt/visual-studio-code/swiftshader/libGLESv2.so
/opt/visual-studio-code/swiftshader/libvk_swiftshader.so
Re: The best Parts of Visual Studio Code are proprietary
#194I was at Pycon - even at the MS booth! - when the Remote stuff was announced. There was a lot of pushback on why it wasn't open. At the time the story was, opening it didn't provide much benefit at the start, but was possible in the future; I recall the all-over-the-place nature of the code was stated as one of the "there's no benefit" (eg they don't want 100 pull requests to fix trivial things or formatting or issues they already know about).
They may never open it. Open source isn't magic pixie dust you sprinkle on software to make it better, but it does make for a weird experience to see them open some things and not others.
Re: The best Parts of Visual Studio Code are proprietary
#195Earlier quoted context omitted.
isn't that the same thing with chrome vs chromium? chrome as a whole is not Open Source or Free Software while chromium is. whether that matters to you is up to you. those who want to use Free Software or Open Source should use Chromium and VSCodium
This divisive "us and them" stance is unnecessary, and doesn't help anyone. OSS and free software matters to me - so I use VSCode, which is OSS. Whether extensions are OSS or not is immaterial (the same extensions you can use with VSCodium!).
the compiled version of chrome is not Free Software or Open Source. only a version from sources only is. you can't build chrome from those sources, only chromium.
now it is possible that VSCode is different in that regard. but if that were the case then VSCodium would not need to exist. so i guess that it is not possible to build a full version of VSCode from those sources either. i'd love to be wrong on that though
Re: The best Parts of Visual Studio Code are proprietary
#196The extension by design is made to be optional to use and are not integral (I would argue) to the vanilla experience of VS Code. That also means that if other people wants to create their own proprietary extensions they can do so. The basic experience of the plain VS Code does not change. Now one can say indeed that the Remote and also LiveShare is the best extension there of, and since the extension author decides n…
code-server has most extensions available. They do it by scraping GitHub for extensions and building them. https://github.com/cdr/code-server/blob/3da6c561b83d2a4c57f3... The Microsoft extensions are notably missing, but they have a lot of other ones. There's an issue template for requesting another one if you find something missing. Not sure if their second extension store is available for use by software other than…
It is indeed, anyone should feel free to use it.
I work at @cdr
Re: The best Parts of Visual Studio Code are proprietary
#197I don't think this is a fair assessment. This post is about two plugins (`LiveShare` and `Remote`), both by Microsoft, not being open source. None of these plugins are even mentioned on Microsoft's Visual Studio Code homepage [0]. At least LiveShare is marketed as a separate tool for which a Visual Studio Code plugin exists (as well as a Visual Studio plugin). [0] https://code.visualstudio.com/ [1] https://visualstud…
Microsoft's Python support just went closed source(pylance vs python language server) the closed sourceness is creeping in on multiple sides. IntelliCode is another closed source aspect.
More precisely, the Python extension is open source but the Pylance language server is not:
https://github.com/Microsoft/vscode-python https://github.com/microsoft/pylance-release
Re: The best Parts of Visual Studio Code are proprietary
#198Earlier quoted context omitted.
Yes this is exactly the risk: developers become dependent on the VSCode extension ecosystem, while thinking they are safely using only FOSS tools. This is the kind of double-speak which lets MS have the best of both worlds. From a marketing/developer relations perspective, developers think they are using open-source tools. But in actuality, developers are investing in workflows where MS is a critical link in the chai…
As the author puts it: "It makes me less certain that this isn't the Extend in Embrace, Extend, Extinguish."
"Extinguish" is often not the case in this decade.
It's all about capturing market share aka creating user lock-in.
Re: The best Parts of Visual Studio Code are proprietary
#199The extension by design is made to be optional to use and are not integral (I would argue) to the vanilla experience of VS Code. That also means that if other people wants to create their own proprietary extensions they can do so. The basic experience of the plain VS Code does not change. Now one can say indeed that the Remote and also LiveShare is the best extension there of, and since the extension author decides n…
code-server has most extensions available. They do it by scraping GitHub for extensions and building them. https://github.com/cdr/code-server/blob/3da6c561b83d2a4c57f3... The Microsoft extensions are notably missing, but they have a lot of other ones. There's an issue template for requesting another one if you find something missing. Not sure if their second extension store is available for use by software other than…
code-server also lets you customize the marketplace URL at runtime.
https://github.com/cdr/code-server/blob/master/doc/FAQ.md#ho...
SERVICE_URL=https://open-vsx.org/vscode/gallery
ITEM_URL=https://open-vsx.org/vscode/item
See this thread: https://github.com/microsoft/vscode/issues/31168#issue-24453...
Re: The best Parts of Visual Studio Code are proprietary
#200Earlier quoted context omitted.
All FOSS is OSS, but not all OSS is FOSS.
Right, but VSCode is MIT licensed. The gripe in the article is about extensions not also being MIT licensed - an argument precisely nobody would be making if it wasn't Microsoft; as someone else here pointed out, you could make the same argument about SQLite, but nobody would.
It’s important to note which code is MIT licensed, and which isn’t, as others have mentioned around components of the extension functionality itself.
I’m not making the specific claims you are arguing against, and I don’t disagree with what you say, in any case. Just as in SQL, and in this case, these licenses matter. A feature matrix clarifying features and licenses would be mice. Also, it would be nice to have a fully FOSS mode for VS Code in its settings or config. It is a distinction with a difference.