3 ms·
VSCodium, aka VSCode without the Microsoft proprietary bits, uses https://open-vsx.org/ https://open-vsx.org/ as the extension registry. The hard problem is co
by TAForObvReasons 4y ago
VSCodium, aka VSCode without the Microsoft proprietary bits, uses https://open-vsx.org/ https://open-vsx.org/ as the extension registry. The hard problem is convincing devs to cross-publish
- dromtrund 4y agoI have published some extensions with about 300k users in total. So far, I've only had two people ask me to publish on open-vsx. I did make one attempt, but something broke in the signup procedure, and it took 3 weeks for someone from support to come back to me with a fix, so I had moved on. If more people were asking for it, I would try again, but the time spent per user to set up a pipeline for each extension just doesn't make sense at the moment. I'd rather spend those nights adding features for the existing mainline users. Cynical perhaps, but there's no reward for making extensions, so there's a limited amount of time I can spend on it.
- andrew_ 4y agoI have a few extensions, notably an update to subtle-brackets, which I cross-published. It's relatively painless - Eclipse running Open VSX is clunky, but no more clunky and UX-weird than the marketplace (which holy shit, talk about terrible UX). The issue is that VSCodium has holes, and not all extensions will run correctly. I'd like to see a hard fork for VSCodium, where the community could make UX/DX upgrades that VSCode's Microsoft-employed gatekeepers have summarily shut down time and time again (see: issues on the find/replace dialogs)