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

91–100 of 158 posts

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

#91

Post by int_19h »

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…

It's even worse. VSCode used to be more open source originally, back when it was enthusiastically adopted. And then, gradually, official extensions started replacing parts with closed blobs with onerous licensing terms. C# and Python extensions have both suffered from this. Although the C++ one was never fully open, if I remember correctly.

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

#92

Post by bayindirh »

mrlongroots wrote: post #48
fr4nkr wrote: 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…

When people started to toot the horn of VSCode, esp. younger, inexperienced people, I personally warned quite a few of them about Microsoft's practices and motivations. Of course, who listens to a graybeard who's talking about impending doom? All answered " Microsoft And here we are.

I hate to be right about things sometimes.

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

#93

Post by arccy »

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…

Microsoft has never been pro open source, yet so many devs fell for their marketing lies.

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

#94

Post by rockyj »

john-h-k wrote: post #44

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.

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

#95

Post by exceptione »

sergiotapia wrote: post #27
exceptione wrote: post #2

There 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 have to somewhat defend Eclipse as the Java platform too. Twenty years ago people had hardly any RAM in their machines, and Eclipse definitely suffered for that, because without RAM you run into lots of disk i/o.

The JRE was born in a time of scarce cpu power and low RAM capacities. It has put tremendous optimization pressure on the project. I develop on .net nowadays, but I have the utmost respect of what they pulled off.

I dare you to install an Eclipse product these days. It will run circles around any Electron offering, while offering real parsers (not treesitter), and reliable code intelligence across vast source projects.

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

#97

Post by zdimension »

exceptione wrote: post #95
sergiotapia wrote: post #27

Earlier quoted context omitted.

Why in earth would they stain their efforts with the "eclipse" name. Screenshots look great!

I have to somewhat defend Eclipse as the Java platform too. Twenty years ago people had hardly any RAM in their machines, and Eclipse definitely suffered for that, because without RAM you run into lots of disk i/o. The JRE was born in a time of scarce cpu power and low RAM capacities. It has put tremendous optimization pressure on the project. I develop on .net nowadays, but I have the utmost respect of what they pul…

> while offering real parsers (not treesitter)

Honest question, what's wrong with treesitters?

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

#98

Post by esperent »

jeroenhd wrote: post #87
loloquwowndueo wrote: post #4

Remember vs code is designed to fracture and the forks are an integral part of that. https://ghuntley.com/fracture/

I fail to see the problem with this, to be honest. Microsoft provides a free IDE for everyone to use on any platform, but it's not good enough because the language runtimes and proprietary third party tools aren't completely free? 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 a…

> at least Microsoft wouldn't take the heat for not doing enough free work for everyone else

You're massively misunderstanding the goals of these large companies who provide open source projects, whether it's VSCode, Android, Chrome, or whatever. The goal is always control. Companies at this scale never do free work for the common good.

I don't say this to deride them, I say it as a statement of fact that we all need to be aware of when we choose to use these products.

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

#100

Post by exceptione »

zdimension wrote: post #97
exceptione wrote: post #95

Earlier quoted context omitted.

I have to somewhat defend Eclipse as the Java platform too. Twenty years ago people had hardly any RAM in their machines, and Eclipse definitely suffered for that, because without RAM you run into lots of disk i/o. The JRE was born in a time of scarce cpu power and low RAM capacities. It has put tremendous optimization pressure on the project. I develop on .net nowadays, but I have the utmost respect of what they pul…

> while offering real parsers (not treesitter) Honest question, what's wrong with treesitters?

Very short answer: because a treesitter will do an approximately correct parsing, while a hand written parser will do a correct parsing (and if not, it is a bug).

For a full, balanced overview, see: https://blog.jez.io/tree-sitter-limitations/

Post reply on HN