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

OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

status.open-vsx.org

Post reply on HN
Print view View original

31–40 of 158 posts

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#31

Post by charcircuit »

dizhn wrote: post #15
amadeuspagel wrote: post #14

Earlier quoted context omitted.

> VSCode is Android Yes, an open source project that creates immense value, but fails to fulfill some purist fantasy.

Like have a working keyboard?

Components that are not used, that almost always get replaced by vendors do not get much love. That the base AOSP should be optimized to use out of the box is a purist fantasy. In reality AOSP is made with the understanding that vendors are going to customize it. A lot of Android is designed to be modular, you can easily install a different keyboard app.

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#32

Post by shiandow »

gchamonlive wrote: post #28

Now it's as good a time as ever to try out Lazy Vim. Came to it from Lunar Vim and it just works. Working with anything is a breeze. I'm just not too familiar with refactoring tooling and how to configure it, but there's rarely any reason for me to use something more complicated than sed, and in those occasions I can just use ast-grep.

Trying out emacs again after vsvode broke remote ssh for no apparent reason (other than their insane decision to install the whole text editor remotely). Tramps in emacs has some quirks (need to make connection timeouts faster somehow) but it just works.

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#33

Post by mappu »

bangaladore wrote: post #13
imcritic wrote: post #11

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

> However, its early days.

Theia has been out for eight years now,

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#34

Post by eddythompson80 »

fr4nkr wrote: post #12

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

Yes, VSC is less "open source" than emacs. if "open sourceness" is a score out of 10 or something. Pretty sure RMS would argue linux is less "open source" than emacs too.

Not sure why this is futile for the VSCodium devs. They are taking a dependency on a service for installing extensions. The solutions is more readonly mirrors for the official OpenVSX endpoint.

If your main archlinux mirror is down, you don't cry about the centralized state of our life. You use a different mirror. You throw in 5 or 10 in case one or two are down. I understand why a company like Microsoft might want a more centralized service to distribute the extensions. But for an open source clone? is Microsoft also expected to create the mirror clone?

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#35

Post by cdelsolar »

ohgr wrote: post #20
joshstrange wrote: post #7

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.

A good analogy. I always felt a little dirty using VScode. Back to tmux, vim a few months back like it has been for the last 20 odd years.

How do you run Cline on it

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#36

Post by ohgr »

cdelsolar wrote: post #35
ohgr wrote: post #20

Earlier quoted context omitted.

A good analogy. I always felt a little dirty using VScode. Back to tmux, vim a few months back like it has been for the last 20 odd years.

How do you run Cline on it

I don’t use any AI agents to write code. I spend most of my time undoing shit shows left by people who do.

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#38

Post by 999900000999 »

fr4nkr wrote: post #12

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…

You can always clone the extensions repo and build locally. Should take 10 minutes at most

I’m not sure how this could actually work without a centralized repo.

If I’m going to use VSCode I’ll just use it, I don’t need to play with forks, etc

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#39

Post by NoboruWataya »

Havoc wrote: post #37

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

Re: OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

#40

Post by teruakohatu »

eddythompson80 wrote: post #34
fr4nkr wrote: post #12

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…

> is Microsoft also expected to create the mirror clone?

Allowing open source VS Code (ie. VS Code you compiled from Microsoft’s repo) to access extensions would be enough. Nobody is asking Microsoft for more than basic access. It’s does not even require a code changes, just a policy change.

Even Google allows Chrome forks to access the Chrome Store.

Post reply on HN