I'm sure some (many?) will disagree with me but: VSCode is Android. Or rather, VSCode's source is AOSP and the marketplace, plugins, etc are Google Play Services. I say that with maximum derision.
> VSCode is Android Yes, an open source project that creates immense value, but fails to fulfill some purist fantasy.
OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
121–130 of 158 posts
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#122Earlier quoted context omitted.
> You can use it as a FOSS editor, but only if you are willing to accept a vastly subpar experience. Why is this Microsoft's fault, though? Nothing is stopping the open source community from creating a more resilient extension distribution system.
The problem isn't the distribution system, it's the licenses on the flagship Microsoft extensions that provide C/C++, Python, Javascript/Typescript, etc. support. Those licenses are entirely Microsoft's fault.
There is no reason we should expect Microsoft to invest tens of millions of dollars into a product development and give it free for competitors like Cursor. That's not just rational, even for companies that are not Microsoft.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#123Open Source projects used to all be hosted on hundreds of random mirrors. The hosting of which was free and donated, because it was just an HTTP/FTP/RSYNC directory on a file server in a closet in some corporation or university. Didn't even need to be reliable, as there were hundreds of mirrors. Linux distributions, and some very old projects, are still maintained this way. Nowadays you must have a flashy website. Yo…
You keep saying _must_. Why _must_ you do what everyone else does? To what end? To get contributors to your project? To get funding? No one is stopping anyone from starting a project on sourceforge.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#124Open Source projects used to all be hosted on hundreds of random mirrors. The hosting of which was free and donated, because it was just an HTTP/FTP/RSYNC directory on a file server in a closet in some corporation or university. Didn't even need to be reliable, as there were hundreds of mirrors. Linux distributions, and some very old projects, are still maintained this way. Nowadays you must have a flashy website. Yo…
> Nowadays you must have a flashy website. You must host everything on a single managed VCS provider, or a programming package ecosystem hoster. You must depend on corporations to give you free things, in exchange for you giving them everything about you (otherwise you must pay out of pocket for everything). You must do what everyone else does. You keep saying _must_. Why _must_ you do what everyone else does? To wha…
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#125Open Source projects used to all be hosted on hundreds of random mirrors. The hosting of which was free and donated, because it was just an HTTP/FTP/RSYNC directory on a file server in a closet in some corporation or university. Didn't even need to be reliable, as there were hundreds of mirrors. Linux distributions, and some very old projects, are still maintained this way. Nowadays you must have a flashy website. Yo…
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#126Earlier quoted context omitted.
Genuinely curious, how did Microsoft "shoved it down everybody's throats"? And weren't Jetbrains, Eclipse, Vim, Emacs dominant enough(especially Jetbrains) to have done so before Microsoft?
VSCode garnered such a significant market share that supporting VSCode almost immediately becomes your #1 editor (see Rust surveys: 2016-3%, 2017-30%, 2018-45%, 2020-54%, 2023-62%--note: VSCode was only released in 2016!). Since the LSP was the only effective way that you could support syntax highlighting in VSCode, languages had to create an LSP or they didn't exist to VSCode users. Once the language supports VSCode…
As a point of comparison, the value that I get from JetBrains products is about 35% UX niceties[1] and 1500000% code intelligence, which no LSP that I have ever seen even strives to do that. They all appear to be focused on "jump to declaration", "what can I type here", and some of them ferry "linter" results back to the user but that is just using LSP as a conduit not that the LSP itself is doing anything intelligent
That's why I throw up in my mouth when someone claims their vim+lsp is a python powerhouse because, sure, it's better than nothing but even PyCharm open source blows the doors off of any LSP
1: and even that has been under constant attack over the past few years from their gravely misguided product management team, culminating in the "you are committing code wrong" https://news.ycombinator.com/item?id=43710699
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#127Earlier quoted context omitted.
> Yes, VSC is less "open source" than emacs. if "open sourceness" is a score out of 10 or something. VS Code is not Open Source, period. What exists in the “Visual Studio Code - Open Source” repo that is MIT licensed but cannot be used to build VS Code. Once-upon-a-time it was just branding, telemetry, and a license to use the Microsoft Extension Marketplace. Now, however, there are proprietary, closed-source extensi…
violating a corporation's terms of service isn't unlawful. outside of that corporation, at least.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#128This right on the heels of the GitLab 17.11 release announcement [0] which mentioned that they added OpenVSX support to their Web IDE. One of the biggest blockers for my team to use the Web IDE/GitLab's equivalent of "Codespaces" was the lack of extensions support. As developers, we're spoiled for widespread (e.g.) vim keybindings support in just about any IDE via extensions. When unable to use it in something like W…
Also, I wonder how hard it would be to teach VSCodium/Theia to pull extensions from OCI because it seems to work great as a distribution mechanism for Homebrew and allows shipping a .vsix from your own GitHub/GitLab account, since both of those offer no-cost OCI image registries scoped to the project
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#129Earlier quoted context omitted.
violating a corporation's terms of service isn't unlawful. outside of that corporation, at least.
It is not criminal, but it is unlawful.
The TOS is purely a thing that the owner can point at as a legitimate reason for banning you.
There is no law anywhere binding you to the terms of an EULA or TOS. It's even less binding than a verbal agreement and a handshake.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#130I'm sure some (many?) will disagree with me but: VSCode is Android. Or rather, VSCode's source is AOSP and the marketplace, plugins, etc are Google Play Services. I say that with maximum derision.