I noticed this the other day when I installed VSCodium on my new Windows box. I had a functional setup for one day , then the next day I couldn't install a language extension I direly needed. It's left a very sour taste in my mouth. I've used Emacs for ages and despite being a much more niche editor, it's never been so hard-dependent on centralized repositories, and the centralized repositories it does have (ELPA/MEL…
I feel that you're conflating few concepts, hackability, "open source", single point of failure architectures. Yes, VSC is less hackable than emacs, but I don't think it's necessarily the same thing. VSC (and others like it) are going for a more streamlined "App Store" experience, while emacs is going for a more DIY/hackable style editor. You can always fetching the VSIX file and sideload it is if the "store" is down…
OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
81–90 of 158 posts
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#82I noticed this the other day when I installed VSCodium on my new Windows box. I had a functional setup for one day , then the next day I couldn't install a language extension I direly needed. It's left a very sour taste in my mouth. I've used Emacs for ages and despite being a much more niche editor, it's never been so hard-dependent on centralized repositories, and the centralized repositories it does have (ELPA/MEL…
Just because pylance is available doesn't stop jetbrains/Google/OSS from creating an LS. Maybe no such exists as if now, but not from a technical blocker. Just no one created one.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#83There is not much to see on a server that is down, so let me share some free advice instead. Visit Eclipse Theia in the mean time when you are serious about de-risking from VSCode. I think VSCodium is doing an uphill battle here, while Microsoft can't help them self being a sales company first. In Theia, everything is open and free of spyware. MS is under no obligation to provide an OSS editor, but playing tricks aft…
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#84Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#85Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#86Earlier quoted context omitted.
> MS is under no obligation to provide an OSS editor, but playing tricks after luring people in is not nice. Microsoft is partly to blame, but people have been warning about this over and over and over ad nauseam and people still choose to use VSCode. You couldn't even get people to not use the proprietary extensions for C/C++, Python and remote development. The problem is that Microsoft dedicates enough resource to…
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?
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, anyone not already steeped in the editor wars switched.
At that point, the editors had to support the LSP or get left behind.
With JetBrains, the issue is that they would have almost certainly considered an LSP as a competitive advantage. It would have taken some amazing foresight to release something like that as OSS and not be afraid of losing market share if you get vim/neovim to adopt it (you can ignore emacs market share--the editor wars are all but over and emacs lost badly).
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#87Remember vs code is designed to fracture and the forks are an integral part of that. https://ghuntley.com/fracture/
Maybe Microsoft should've made VSCode source-available. Sure, companies taking Microsoft's free labour would need to develop an IDE of their own (or maybe someone can hack Eclipse to work as a browser project?), but at least Microsoft wouldn't take the heat for not doing enough free work for everyone else.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#88Earlier quoted context omitted.
Why would I switch from vscodium to theia?
Theia is not a fork of vscode (even though it looks like it). It uses VSCode's code editor (Monoco) and is written from the ground up. Presumably allowing it to support extensions, that for example, vscode does not. However, its early days.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#89I'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.
Its value and main goal is to suffocate any initiative on mobile space, call it immense if you will, but I concede it certainly works.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#90Earlier quoted context omitted.
I feel that you're conflating few concepts, hackability, "open source", single point of failure architectures. Yes, VSC is less hackable than emacs, but I don't think it's necessarily the same thing. VSC (and others like it) are going for a more streamlined "App Store" experience, while emacs is going for a more DIY/hackable style editor. You can always fetching the VSIX file and sideload it is if the "store" is down…
> Pretty sure RMS would argue linux is less "open source" than emacs too. The word you're looking for is 'free'. Free as in freedom and free software. The open source philosophy focuses on the openness of the code base and the associated advantages. Free software philosophy highlights the freedom that the software gives its user on their devices . Opening the source code is just a means to that end for the free softw…