This is why I've been learning neovim for the past couple weeks - the vscode reliance on Remote SSH extension felt like lock in
There are a couple of options for Remote SSH with neovim:
OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
51–60 of 158 posts
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#52I 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…
For context, Open VSX is run by the Eclipse foundation, which also develops the Eclipse Theia editor, which is basically a clone of VS Code (not a fork, like VS Codium). The Open VSX registry is open source ( https://github.com/eclipse/openvsx ) and self-hostable, although I have no experience with that. I assume it's possible to host your own instance with the extensions you want instead of relying on the free publi…
Even though I've heard of Theia Editor before I don't think I've ever seriously looked at it until now. It honestly looks like a good alternative to vscode. (It basically looks like a straight up clone, which is good for me) I'll definitely give it a try.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#53Earlier 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…
My point about VSC is that brands itself as "open source" when Microsoft clearly intends for it to have a proprietary, tightly controlled ecosystem. It's not just RMS-unapproved, it's practically a lie. You can use it as a FOSS editor, but only if you are willing to accept a vastly subpar experience. Oh, and they've started cracking down on people using their proprietary VSC plugins in derived editors, too. I expecte…
I wonder if more differentiated branding would have helped. Chrome/Chromium is another example that came to mind: Like "Code - OSS" (the open-source base of VSCode), Chromium works just fine as a browser but with fewer Google-related features (syncing, DRM, etc). People seem to happily use Chromium despite the limitations (many actively seek them!), and I don't remember there being a controversy like this.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#54I 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…
Pointless was my thought after initially installing it years ago. Ok, I’m installing this open source “clean” version, just to install a bunch of MS proprietary spyware extensions? Why not just use the real thing?
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#55https://github.com/lapce/lapce is an interesting contender in this space
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#56Earlier 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…
> (I was going to also say "or the OSS guys all unify behind a choice" but Hell will freeze over before that happens.) The editor war is going as strong as ever, emacs vs vim will still be here in 20 years. Compared to 10 years ago, the amount of people using emacs and vim only grew, although VSCode growth was 1000x faster.
I was watching the "Simple Made Easy" talk by Rick Hickey, and while he was talking more about programming languages, the talk could extend easily to editors and other type of tooling. People are always going for easy, not simple.
Vim is very simple (a composable language for editing, straightforward integration with cli tools, easily extendable,...). Emacs is simple (Major mode that dictates main operations and display, minor modes for additional features, integrations between them can be described more as a complex web than a simple graph...).
VS Code is easy (helpful suggestion for plugins, Familiar IDE-like interface, default setup, ready to hack on projects,...), but scratch that surface and the complexity appears (behemoth web engine, settings all over the place, app store like marketplace, extension are full blown software project,...). All the cons of IDE with none of the pros.
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#57I happened to be poking around in their issues to see if there were mirrors and observed that in addition to the linked status page on this thread, the underlying Eclipse Foundation has their own (multiple) status tracking channels
most relevant: https://www.eclipsestatus.io/incident/549796?mp=true
their helpdesk ticket: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5924...
the issue in their GitHub issue tracking for the site: https://github.com/EclipseFdn/open-vsx.org/issues/3805
the tl;dr seems to be a massive storage failure affecting a bunch of Eclipse services, and just like any storage problem putting all the bytes back is some "please wait"
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#58There 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…
Why in earth would they stain their efforts with the "eclipse" name. Screenshots look great!
I in some sense empathize with you, in that Eclipse have a minor branding problem, a major discoverability problem for all of their projects of subprojects of projects to track the projects. That said, Eclipse the editor was all in on building a platform[1] upon which other people could build their own editors. It was quite popular before Electron arrived and sucked all the oxygen out of the rich text delivery space
Eclipse the IDE also sat on their laurels and got their lunch eaten by JetBrains on the functionality front and VSCode on the extensible platform front
1: https://wiki.eclipse.org/Rich_Client_Platform/> or https://en.wikipedia.org/wiki/Eclipse_(software)#Rich_client...>
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#59This is why I've been learning neovim for the past couple weeks - the vscode reliance on Remote SSH extension felt like lock in
Do you have a particular configuration or set of extensions you've been looking at? I mostly use JetBrains IDEs but have been trying to get a decent neovim setup as well. I followed some random tutorial and eventually got a decent setup working but it feels fragile and I'm not sure I could reproduce it if I had to. I am looking at AstroNvim now as a potentially more stable/reproducible setup.
With editors like vim, neovim, emacs, it's way easier to get the lay of the land first (tutorial, play around with the default config,..) and then list out what you need.
My vim config has three things only: LSP, FZF (for anything fuzzy), and Plug (to install the above two). There's also a few niceties, but I could do without them. or vendor them into the main config. But it's not my daily editor, so that's just the base config. Anything I could add on top of that would depend on the projects I would need it for. That's about 200 lines (the lsp config is 1/4 of that)
NB. A nice talk even if it's about vim "How to Do 90% of What Plugins Do (With Just Vim)"
Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
#60I 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…
For context, Open VSX is run by the Eclipse foundation, which also develops the Eclipse Theia editor, which is basically a clone of VS Code (not a fork, like VS Codium). The Open VSX registry is open source ( https://github.com/eclipse/openvsx ) and self-hostable, although I have no experience with that. I assume it's possible to host your own instance with the extensions you want instead of relying on the free publi…
Theia is based on Microsoft Monaco editor. Its a fork with a different ui