Or you could just, you know, actually use Linux or BSD.
Or you could just, you know, actually use Linux or BSD.
You mind pointing out in the code where it "phones home to Microsoft to let them know what you've been doing with it"?
https://github.com/microsoft/terminal/blob/master/src/termin...
See also the corresponding hpp files.
The files you're linking to--specifically in terminal/parser--serve to tell a local developer running a text-mode application what VT sequences are in common use to help that developer figure out where to apply effort. We can also request that people enable these traces and explicitly view their contents, then choose to send us the data to help us troubleshoot VT parsing issues.
There trace logs aren't even wired up to the "telemetry" stream that everybody's so afraid of: TraceLogging is a local data capture solution first and foremost, and anybody can look at what's being produced using Windows Performance Analyzer. Nothing from this tracing provider leaves the user's computer.
[1] https://news.ycombinator.com/item?id=19322398, https://news.ycombinator.com/item?id=19324538
Some of the recent changes I've seen happening at an increasing scale is having practical support levels:
- fully-managed
- half-managed
- BOYO (Being on your own)
This is then applied to both company-delivered systems as well as BYOD systems. Combined with standard interrogation tools like osquery you can get a much better picture of what is happening and what level of compliance you can measure.
Instead of them implicitly trusting or hoping a device is okay you actually get to measure it. This enables a BOYO-BYOD BSD fanboy to present themselves as being in-spec and compliant while being in their own comfortable environment for maximum productivity. At the same time, someone who has a hard time figuring out how to turn a laptop on just goes for fully-managed, still gets measured periodically and on-access and gets a generic experience allowing normal-people productivity.