3 ms·
They’re extensions, nothing prevents you from reimplementing proprietary extensions as open source packages. As a matter of fact, there’s probably an oss altern
by thiht 3y ago
They’re extensions, nothing prevents you from reimplementing proprietary extensions as open source packages. As a matter of fact, there’s probably an oss alternative for each proprietary extension already. Maybe it’s not on par with the proprietary extension, but then… work on it?
- bayindirh 3y agoOfficial VSCode builds are also closed source binaries, which comprise of latest VSCodium stable plus Microsoft's secret sauce (per their wording). And, I don't prefer to feed closed source ecosystems with open source plugins, since the core is not open to begin with. It's not that I'm in need of an IDE-like code editor. I got that part covered already. Also for larger needs, I use the same tool for the last 20 years, which is Eclipse. Lastly, while I love to support Free Software, I have limited time and have to choose my battles wisely. So, instead I build the tools I need in my personal and professional life instead of developing plugins. If I have more time, I'd rather develop plugins for Eclipse, though.