Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The best Parts of Visual Studio Code are proprietary

underjord.io

Post reply on HN
Print view View original

241–250 of 277 posts

Re: The best Parts of Visual Studio Code are proprietary

#241

Post by jefftk »

pjmlp wrote: post #236
jefftk wrote: post #222

Earlier quoted context omitted.

Firefox does not use WebKit (and at this point neither does anyone else), but they can look at patches to WebKit to understand how Apple improved Safari's performance. Because Apple produces the hardware, the OS, and the browser, the choices they make in the WebKit implementation are highly informative. > it shows how being FOSS isn't enough This is true for every app on iOS: even if you have the source code, you can…

No they cannot unless they want to contaminate their development, as far as I recall the licenses aren't compatible. It is true for any commercial application with source code available since there are computers. If the user freedoms were of any value as you mention, WebKit and Bink would use copyleft licenses.

Just because you can't literally copy the code from one place to another doesn't mean you can't learn from it. I'm not a lawyer, but my understanding is it's fine to learn what series of system calls they're making and look at their optimizations.

Re: The best Parts of Visual Studio Code are proprietary

#242

Post by zimbatm »

I know that the author wants to use VS Code. But for those reading here and live in the terminal, tmate[1] is truly incredible. Install and type `tmate`, and you have a tmux session that people can SSH into. I have used it countless times and is a great complement to a video sessions. Much better than pixelated fonts in a screen share.

[1]: https://github.com/tmate-io/tmate

Re: The best Parts of Visual Studio Code are proprietary

#243

Post by acdha »

WorldMaker wrote: post #237
acdha wrote: post #197

Earlier quoted context omitted.

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

Pylance is built upon the Pyright language server which is open source: https://github.com/microsoft/pyright I'm curious what research/IP has lead to this being a source turducken of open-closed-open, but it's not entirely closed.

Has anyone said definitively that it wouldn't be open-source in the future? I know sometimes this is due to things like joint or contract development where the lawyers need to hash out the rights first.

Re: The best Parts of Visual Studio Code are proprietary

#244

Post by electronstudio »

TAForObvReasons wrote: post #240
electronstudio wrote: post #131

Earlier quoted context omitted.

They don’t brag about it as much as Microsoft do but IntelliJ Community Edition is free software. https://github.com/JetBrains/intellij-community/blob/master/...

... and open source (Apache 2.0 License)

All free software is open source, by definition.

Re: The best Parts of Visual Studio Code are proprietary

#245

Post by Gaelan »

kls wrote: post #186
skohan wrote: post #182

Earlier quoted context omitted.

> When I add an extension to my IDE, I make sure I understand the licencing implications. The UX decisions of VSCode go against this kind of careful consideration of licencing implications. If I open a code file and VSCode has a suggested extension for the file type, I will see an animated popup in the bottom of the screen, with a button to install. The simplest way to get rid of this popup is to simply install the e…

I guess it is just me, but I have never clicked on that pop-up. I always go to the extension tab and add extensions there, where the second link at the top, has a direct link to the licence of said extension. I always go to the extensions tab because it provides documentation about the extension, which I want to read before I add it to my IDE.

Even that page doesn’t tell you the license. It just has a link to “license”, and given that VS Code is marketed as open source software, and there’s often even a GitHub link (for issues), it’d be pretty easy that the “license” linked to was GPL or MIT or something.

Re: The best Parts of Visual Studio Code are proprietary

#246

Post by zeroego »

zimbatm wrote: post #242

I know that the author wants to use VS Code. But for those reading here and live in the terminal, tmate[1] is truly incredible. Install and type `tmate`, and you have a tmux session that people can SSH into. I have used it countless times and is a great complement to a video sessions. Much better than pixelated fonts in a screen share. [1]: https://github.com/tmate-io/tmate

I can't wait to try this, thanks for sharing!

Re: The best Parts of Visual Studio Code are proprietary

#247

Post by hoistbypetard »

jasode wrote: post #103
CiTyBear wrote: post #14

Earlier quoted context omitted.

I don't think it says "Software not open-source is bad". But more something like "It is marketed as open source but it is not". Developers should be aware that VSCode is not as open source as it claims it is. In my circles, developers could swear VSCode is fully open source without even knowing VSCodium. If people were more aware about this, they might think twice before using VSCode for everything and getting lock-i…

>But more something like "It is marketed as open source but it is not". Developers should be aware that VSCode is not as open source as it claims it is. Honest question... Is SQLite also deceiving people about its "open source credentials" because the Encryption Extension is proprietary and costs $2000?[1] ... because as far as I can tell, most conversations do refer to SQLite as "open source" without always bringing…

Just going by "feel" without rigorously analyzing why it feels this way, my personal answer to your question is that the sqlite encryption extensions feel very much like LiveShare and not so much like Remote. Remote feels to me like a major part of the product that MS advocates without differentiation. LiveShare feels like a neat add-on that's a nifty alternative to several other similar things.

Similarly, the encryption extension has many alternatives and I've never heard Dr. Hipp advocate using it. This thread is the first I've heard of it, and I've heard of alternatives before. Where I knew coming in about Remote and LiveShare based on promotions from Microsoft.

That's just an explanation of how it "feels" to one reader, not any kind of careful analysis or sweeping statement.

Re: The best Parts of Visual Studio Code are proprietary

#248

Post by pjmlp »

jefftk wrote: post #241
pjmlp wrote: post #236

Earlier quoted context omitted.

No they cannot unless they want to contaminate their development, as far as I recall the licenses aren't compatible. It is true for any commercial application with source code available since there are computers. If the user freedoms were of any value as you mention, WebKit and Bink would use copyleft licenses.

Just because you can't literally copy the code from one place to another doesn't mean you can't learn from it. I'm not a lawyer, but my understanding is it's fine to learn what series of system calls they're making and look at their optimizations.

Reading the code means analog copy paste.

Re: The best Parts of Visual Studio Code are proprietary

#249

Post by WorldMaker »

acdha wrote: post #243
WorldMaker wrote: post #237

Earlier quoted context omitted.

Pylance is built upon the Pyright language server which is open source: https://github.com/microsoft/pyright I'm curious what research/IP has lead to this being a source turducken of open-closed-open, but it's not entirely closed.

Has anyone said definitively that it wouldn't be open-source in the future? I know sometimes this is due to things like joint or contract development where the lawyers need to hash out the rights first.

No plans according to a comment in July [1].

Curiosity leading me to try to answer my own question with an educated guess: Pylance does appear to use the ONNX runtime, so it seems probable that it could be using ML models for type information to feed to Pyright developed by or in concert with IntelliCode efforts and that research effort of IntelliCode does fit what Microsoft is currently keeping proprietary.

[1] https://github.com/microsoft/pylance-release/issues/4#issuec...

Re: The best Parts of Visual Studio Code are proprietary

#250

Post by esalman »

Lately I have become fully dependent on the remote development extension for my research, and this makes me very uneasy. I do not want to be restricted to using proprietary tools in case they change something down the line that is not to my liking. It was a lot of trouble moving on from Matlab to Python already...
Post reply on HN