zlacker

[return to "Performance and telemetry analysis of Trae IDE, ByteDance's VSCode fork"]
1. kiitos+IQ[view] [source] 2025-07-28 01:46:56
>>segfau+(OP)
In the OP screen share, they toggle various telemetry options on and off, but every time a setting changes, there is a pop-up that says "a setting has changed that requires a restart [of the editor] to take effect" -- and the user just hits "cancel" and doesn't restart the editor. Then, unsurprisingly, the observed behavior doesn't change. Maybe I'm dumb and/or restarting the editor doesn't actually make a difference, but at least superficially, I'm not sure you can draw useful conclusions from this kind of testing...

edit: to be clear I see that they X-out the topmost window of the editor and then re-launch from the bottom bar, but it's not obvious that this is actually restarting the stuff that matters

◧◩
2. Aurorn+mR[view] [source] 2025-07-28 01:53:47
>>kiitos+IQ
Thanks for watching and catching that. It seems like a major oversight for the core claim: That disabling telemetry doesn’t work. If a restart is required and the tests ignored the restart warning that would invalidate the tests.

Either way, it’s useful to see the telemetry payloads.

◧◩◪
3. pmxi+6Z[view] [source] 2025-07-28 03:29:37
>>Aurorn+mR
See the authors response. He or she says it doesn’t matter either way

>>44706580

[go to top]