Python Forum
VSCode has become too invasive. - Printable Version

+- Python Forum (https://python-forum.io)
+-- Forum: Forum & Off Topic (https://python-forum.io/forum-23.html)
+--- Forum: Bar (https://python-forum.io/forum-27.html)
+--- Thread: VSCode has become too invasive. (/thread-41125.html)



VSCode has become too invasive. - Larz60+ - Nov-14-2023

I have been getting more and more upset by the invasive nature of VSCode.
It's a shame, because I really like the editor.
If anyone knows how to totally shut telemetry off (other than disabling internet), please let me know.


RE: VSCode has become too invasive. - rob101 - Nov-15-2023

Not that I use this or that I've tried it; simply because I'm happy with the setup that I use, but if I were to try a different code editor/IDE, I'd try VSCodium, which may be what you're looking for?


RE: VSCode has become too invasive. - Gribouillis - Nov-15-2023

I systematically throw away invasive software, however good they are. Too many companies take advantage of their defenseless customers. It is unfair. Use free software!


RE: VSCode has become too invasive. - Larz60+ - Nov-15-2023

Gribouillis Wrote:I systematically throw away invasive software, however good they are. Too many companies take advantage of their defenseless customers. It is unfair. Use free software!
I usually do, but am reluctant (until current project complete).

I think I will return to emacs.
It has served me well for a very long time.

I haven't used lisp (on a regular basis) for at least 10 years, and will have to remember how to use emacs again.
I hear it's a lot easier now, (however the +10,000 commands still exist)

I used original program back in the late 1980's, while at a company in Waltham, MA. (USA), where we had a direct microwave link to MIT's internet. (most had not heard about internet at that time).

I guess it's back to the basics (after I complete current project).

------------
EDIT:Nov 16, A.M. EST:
Rob101 Wrote:Not that I use this or that I've tried it; simply because I'm happy with the setup that I use, but if I were to try a different code editor/IDE, I'd try VSCodium, which may be what you're looking for?
Have been looking at VSCodium and may give it a go.


RE: VSCode has become too invasive. - rob101 - Nov-22-2023

(Nov-15-2023, 08:04 PM)Larz60+ Wrote: Have been looking at VSCodium and may give it a go.

I got a little curious about this editor, so I gave it a try. While it's clearly excellent, with many, many different options and plug-ins, I don't believe that it betters what I use. That said, what I use is Python specific; I use other editors for things such as Markdown, for example, so I don't need the flexibility that VSCodium provides. I'm also a little set in my ways when it comes my Python IDE, which is Wing Personal, if anyone is interested.

I know how Wing works, having used it for over five years, so I can write and test my scripts without having to figure what keys do what. That's not to say that it's without its "wish list", but that list is very short and there are work arounds.


RE: VSCode has become too invasive. - menator01 - Nov-22-2023

I just tried vscodium and it's pretty good. looks and acts just like vscode. Thumbs Up
I tried it out with python, php, html, java, javascript, c, and c++. All worked as expected.

On a side note you can import extentions for vscode with this tutorial. (Not all extensions are in the vscodium repository.
https://milicendev.netlify.app/article/install-vs-codium-and-integrate-vs-code-extensions/


RE: VSCode has become too invasive. - Larz60+ - Nov-22-2023

Thanks all, I will try vscodium, actually already had downloaded the code, but not hadn't compiled it prior to starting this thread.

After using emacs in the early 1980's (and after that from time to time), emacs has been the most stable. Around the mid 1980's, I swore by 'brief' which was a commercial code editor, but absoutly excellent given when it was created. Most of my coding back then was in 'C'.

I am tempted to go back to emacs. I has been, and I think will still be around for many years to come. I am closer to 80 now than I am to 70, so probably will only be writing code for another 15 years or so so emacs will probably still be there then.

Will try vscodium first.