Live data from Hacker News

The best Parts of Visual Studio Code are proprietary

underjord.io

141–150 of 277 posts

Re: The best Parts of Visual Studio Code are proprietary

#141
I 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://visualstudio.microsoft.com/de/services/live-share/

Re: The best Parts of Visual Studio Code are proprietary

#142
post #129

Earlier quoted context omitted.

Exactly. And it's important to write articles like this about VSCode, Android, Chrome, and any others engaging in this (increasingly common) marketing approach.

And users can help by actually using VSCodium, LineageOS, Linux distro Chromium builds, non-Xcode clang, etc. instead of the proprietary variants.

Which the large majority chooses not to, so there you have it, the open source dream.

Re: The best Parts of Visual Studio Code are proprietary

#143

I might have missed a key paragraph, but what is preventing anyone or any company to develop a Remote equivalent for vim or any other editor? If not already done.

That it is proprietary?

> I read a piece of license that said that LiveShare could only be used with the Visual Studio family of products

Re: The best Parts of Visual Studio Code are proprietary

#144

I 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.

Re: The best Parts of Visual Studio Code are proprietary

#145
post #117
post #110

Earlier quoted context omitted.

The main way SQLite is used around the world is as a library component of a larger application. The main way people use VS code is through the proprietarized official build that uses the official EULA. Also, lots of people seem to value the proprietary extensions a lot more than people value the encryption extension of SQLite.

>The main way people use VS code is through the proprietarized official build that uses the official EULA The blog author complained about "Live Share" as one example. As far as I can tell, "Live Share" is not in the builds one downloads from Microsoft's "Visual Studio Code" website: https://code.visualstudio.com/download The Live Share feature is downloaded from a separate web page: https://marketplace.visualstudio.…

> Can someone explain how the situations are not analogous?

The difference is that typical usage of SQLite is co-located with an application, such that you don't need encryption, and it doesn't market itself as a great database to stand up on a far-away server.

VSCode is marketing these extensions with the core product, as features thereof. They seem to be much closer to critical, core functionality. I think that they are functionally similar situations, except that nobody uses/cares-about that SQLite extension.

Microsoft is also marketing as if VS Code is open source. One claim or the other is fine, but the combination is deceptive. There are many closed-source components which are part of VS Code, if indirectly.

Re: The best Parts of Visual Studio Code are proprietary

#146
post #3

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. If we're debating the OSS credentials of VSCode, it'll need to be based on the code already released (which makes it a pr…

It boils down to the (hostile?) takeover of the term "Open Source" by large, shareholder-value driven companies. Admittingly, Stallman has a point when he says "Why Open Source misses the point of Free Software" [1]

[1] https://www.gnu.org/philosophy/open-source-misses-the-point....

Re: The best Parts of Visual Studio Code are proprietary

#148
post #126
post #86

Earlier quoted context omitted.

There is a difference between, say, Debian popcon (which is opt in during install) and the 50 MSFT tracking options that are enabled despite having ticked the "no" box during install. One of which is a keylogger! Windows 10 is pure evil.

Do you have a link for the key logger?

The full list is here https://docs.microsoft.com/en-gb/windows/privacy/required-wi...

Re: The best Parts of Visual Studio Code are proprietary

#149
post #123
post #98

Earlier quoted context omitted.

Google has largely outpaced Microsoft on what concerns Extinguish.

Can you give some examples? I haven’t seen Google close source something lately, except for Go’s package hosting server (which makes me inclined to believe you, I just haven’t heard of other instances).

All the Google apps that used to be open once-upon-a-time in Android and whose evolved versions are all closed source now.
Post reply on HN