3 ms·

Because it's hard. I use tons of tools in my digital ecosystem, and the divide is tiring sometimes. Tool switching adds a little overhead, which can become not

Because it's hard. I use tons of tools in my digital ecosystem, and the divide is tiring sometimes. Tool switching adds a little overhead, which can become not little when you're trying to do a lot of things because life demands it. I use Eclipse as my main IDE, but for smaller stuff I use KATE on Linux and BBEdit in macOS. Similarly, my knowledge base has to be divided between two tools. When you have time, this is no burden. But if you don't, then it starts to bother you. Also, creating digital systems requires time and experience. However, I'm very with you on VSCode thing. It's a proprietary tool looks like a free one, and keeping people imprisoned without they realize. As a fun side note, VSCode's Java language server is a headless Eclipse instance.

fragmede 3y ago
VSCode looks really Free, in what way is it proprietary that you're thinking of? In which language are you using it?
- johnny22 3y ago
  vscodium is really Free. vscode's default python language server for example is not open. I think the remote connection stuff isn't either.
- bayindirh 3y ago
  It's free as in beer, not Free as in speech. Tons of plug-ins are Microsoft proprietary, or being closed down step by step. I'm not and won't be using it.
  - 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 ago
      Official 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.

fragmede 3y ago

VSCode looks really Free, in what way is it proprietary that you're thinking of? In which language are you using it?

johnny22 3y ago
vscodium is really Free. vscode's default python language server for example is not open. I think the remote connection stuff isn't either.
bayindirh 3y ago
It's free as in beer, not Free as in speech. Tons of plug-ins are Microsoft proprietary, or being closed down step by step. I'm not and won't be using it.
- 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 ago
    Official 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.