3 ms·
> However, the telemetry of VSCode is non-personal metrics I don't care, I don't want my text editor to send _any_ telemetry, _especially_ without my explicit
by SoothingSorbet 2y ago
> However, the telemetry of VSCode is non-personal metrics
I don't care, I don't want my text editor to send _any_ telemetry, _especially_ without my explicit consent.
> some of the most popular extensions are only available with VSCode
This has never been an issue for me, fortunately. The only issue is Microsoft's proprietary extensions, which I have no interest in using either. If I wanted a proprietary editor I'd use something better.
- aftbit 2y agoI dropped VSCode when I found out that the remote editing and language server extensions were both proprietary. Back to vim and sorry I strayed.
- all2 2y agoJetbrains is pretty ok on this front. I've been enjoying using my beefy computer to do work from my potato laptop.
- prometheon1 2y agoThe way I read it, the message you replied to was a complaint about parts of VSCode being proprietary. Do you mean to say Jetbrains is pretty ok on the "not being proprietary" front?
- aftbit 2y agoYeah, 100%. I'm not a hardcore FOSS only person, but for my core workflow, when a FOSS tool exists and works well, I am not likely to use a proprietary alternative if I can avoid it at all. So yeah, I'll use Excel to interoperate with fancy spreadsheets, but if LibreOffice will do the job, I'll use it instead. I tried out several of the fancy proprietary editors at various times (SublimeText, VSCode, even Jetbrains), but IMO they were not better _enough_ to justify switching away from something like vim, which is both ubiquitously available and FOSS.
- causal 2y agoMaking the remote editing extension closed is particularly frustrating, as you have little visibility into what it's doing and it is impossible to debug obscure errors