Live data from Hacker News

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

status.open-vsx.org

151–158 of 158 posts

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

#151
post #116
post #74

Earlier quoted context omitted.

https://ghuntley.com/fracture/ ; I'll just leave this here.

Yeah, I know all about that stuff. But nevertheless, you _can_ fork it. Is it the most awesome, selfless, altruistic version of open source? Clearly not. But is it better than being proprietary closed-source software? Well, that's a value judgement, so we can each decide that for ourselves. Personally, I think so, but maybe it depends. Regardless, though, it's open source, and if it weren't the software landscape wou…

> Regardless, though, it's open source

Some major bits and pieces of the base editor are, but little of what makes vscode into a usable productive tool (namely, the refined extensions and LSP implementations around it, i.e. what users come to expect when they install it in the first place) is open-source. vscode put a lot of marketing effort into being perceived as open-source so to buy sympathy from eventual users.

Let's stop at "vscode is open-source in a very narrow and limited capacity, and thoroughly deceptive in its messaging".

I would honestly love to see the result of a survey asking vscode users whether they think they are using an open-source product, and how much of that is actually verified based on the extensions being used.

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

#152
post #41

Earlier quoted context omitted.

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…

Exactly this. For me, the C/C++ language pack stopped working overnight with Cursor. This was clearly because of commercial concerns about derivative IDEs fairly and squarely gaining traction over the original product. But it broke my workflow a couple hours before a meeting. I use neovim with LSPs and this is unimaginable in my world. I have started using IDEs only because the productivity gains from better LLM inte…

I saw someone mention Avante on here a few days ago, which looks like it tries to emulate the Cursor experience in Neovim. Might be worth a look: https://github.com/yetone/avante.nvim

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

#153
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

There's lots of different AI agents now. It's not rocket science and conceptually they're all built the same.

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

#155
post #94

Lots of vim/emacs mentions so I feel obliged to mention Helix ( https://helix-editor.com/ ). Used neovim for _years_, tried Helix for a few weeks and never looked back

Really interested. Can you recommend a good tutorial, I tried searching but could not find anything which looked promising.

Try the helix tutor itself. Install, then do `hx --tutor` (binary is also called helix rather than hx on a few package managers).

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

#156
post #78

Lots of vim/emacs mentions so I feel obliged to mention Helix ( https://helix-editor.com/ ). Used neovim for _years_, tried Helix for a few weeks and never looked back

I love helix, I just wish more editors had support for its bindings so I'm not as out of water when I have to use an IDE.

Strongly agree. There's a new page on the site about helix-mode in other editors (although there are a limited number of entries): https://docs.helix-editor.com/master/other-software.html

I myself have built zsh bindings for helix as that was my main pain point: https://github.com/john-h-k/helix-zsh

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

#157
post #151
post #116

Earlier quoted context omitted.

Yeah, I know all about that stuff. But nevertheless, you _can_ fork it. Is it the most awesome, selfless, altruistic version of open source? Clearly not. But is it better than being proprietary closed-source software? Well, that's a value judgement, so we can each decide that for ourselves. Personally, I think so, but maybe it depends. Regardless, though, it's open source, and if it weren't the software landscape wou…

> Regardless, though, it's open source Some major bits and pieces of the base editor are, but little of what makes vscode into a usable productive tool (namely, the refined extensions and LSP implementations around it, i.e. what users come to expect when they install it in the first place) is open-source. vscode put a lot of marketing effort into being perceived as open-source so to buy sympathy from eventual users.…

> Let's stop at "vscode is open-source in a very narrow and limited capacity, and thoroughly deceptive in its messaging".

OK, yes, I agree; we should stop, as the disagrement seems to boil down to semantics.

I think "open source" is basically binary (modulo the usual free-as-in-beer or free-as-in-beer-but-also-you-can't-do-stuff-I-don't-like ambiguity).

But some nuance does come into play around "VS Code" — what is it? It feels the same as Chrome to me, but it's harder to see where the VS Code equivalent of Chromium is. (Not super hard, mind you, but Chrome/Chromium make it explicit, whereas VS Code does not.)

Anyway, I agree that VS Code is (while still, IMO, "open-source") is not "open-source to the point of maximal awesomeness".

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

#158

Earlier quoted context omitted.

Caveat: this is not universal and depends on the juridiction. For example in France a software/service editor can only really attack a user if he is infringing on copyrighted stuff. Outside of that the EULAs only allow it to ban/remove access to its services without risk of legal retaliation. And by infringing copyright I mean redistribution of copyrighted material, not downloading and using it. I am sure this is the…

This is again, wrong. EULA is just another word for "contract", and I'm not aware of any countries that have banned contracts. Of course, specific EULAs may not be enforceable in some countries because they contain terms prohibited by law. But the concept of EULAs - a contract where you agree to certain terms in exchange for license to use software is enforceable in basically all countries.

A contract is only valid if you sign it, not because someone in his office unilateraly decided you have agreed.
Post reply on HN