Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
even the vscodium maintainers say they found it impossible to block vs code's eager telemetrizing
Source for this? Does VSCodium with no extensions send telemetry, or is it the extension issue?
The funny thing is that I was about to install VSCodium for the first time TODAY, because I want live markdown preview. (I want a doc editor, not necessarily a code editor)
The rationale for VSCodium says it's about telemetry, although strictly speaking it's doesn't promise they removed all the telemetry!
https://vscodium.com/
but the product available for download (Visual Studio Code) is licensed under this not-FLOSS license and contains telemetry/tracking
Should I run it in a container?
The biggest caveat would be to be aware of the default connexion to an alternative extension store, https://open-vsx.org, instead of Microsoft's own store, which does not have all the extensions the official store has. But that's less and less an issue, thanks to projects such as https://github.com/open-vsx/publish-extensions. In the worst case, I just manually `git clone`d the desired extension in my local extension folder. Nothing to complain about otherwise
Summary of the thread based on the previous 100 threads about VSCode telemetry (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...)
Yes, VSCode collects telemetry. There is no way to turn this off. The events are mostly about which features are being used. Microsoft claims that the events are anonymized and this is therefore GDPR compliant.
Critics, especially on HN, speak about the potential privacy violations that this data could enable. In none of the threads I've read have people actually given a mechanism of how this would happen. It's taken as an article of faith that de-anonymization is trivial. Assuming that it's true, it's still unclear how knowledge of the features a person uses in the app can be used to do anything other than improving the app.
My opinion - it's safe to assume Microsoft is GDPR compliant. There's no sense in risking the fines GDPR could potentially levy for the sake of ... what exactly? There's no upside even if this data was somehow de-anonymized. The sensible thing to do is to delete everything within 90 days except for the most basic info (number of unique users over time).
If the message is to be believed (and the source code does agree: https://github.com/microsoft/vscode/blob/d32b92bd7a49ce8667b...), the old settings still apply, the new one may default to 'all' but the old settings will override it.
I struggled to make the change. I think I tried half a dozen times to go from (neo)vim to Emacs and it never stuck. My problem was that I kept reaching for spacemacs and Doom Emacs, etc., right out of the gate, and I would be mystified by Emacs itself and Emacs Lisp as a result.
Two things helped get me into Emacs full-time (and this is after > 15 years of using vim):
1. I went step-by-step through Susam's Emfy Emacs config [0]. That helped me understand some of the basics at a foundational level. I extended that base configuration a little bit and became comfortable with the environment.
2. I then went step-by-step through the entire "Emacs from Scratch" playlist that System Crafters put out [1]. I pushed my personal configuration pretty far with that over the course of 2-3 months.
I eventually moved to Doom Emacs and married in pieces of my own configuration. That's been my daily driver for months now.
[0]: https://github.com/susam/emfy
[1]: https://www.youtube.com/playlist?list=PLEoMzSkcN8oPH1au7H6B7...
The biggest caveat would be to be aware of the default connexion to an alternative extension store, https://open-vsx.org, instead of Microsoft's own store, which does not have all the extensions the official store has. But that's less and less an issue, thanks to projects such as https://github.com/open-vsx/publish-extensions. In the worst case, I just manually `git clone`d the desired extension in my local extension folder. Nothing to complain about otherwise