news: July 2025

Performance and telemetry analysis of Trae IDE, ByteDance's VSCode fork
819 by segfault22 | 297 comments on Hacker News.
Hi HN, I was evaluating IDEs for a personal project and decided to test Trae, ByteDance's fork of VSCode. I immediately noticed some significant performance and privacy issues that I felt were worth sharing. I've written up a full analysis with screenshots, network logs, and data payloads in the linked post. Here are the key findings: 1. Extreme Resource Consumption: Out of the box, Trae used 6.3x more RAM (~5.7 GB) and spawned 3.7x more processes (33 total) than a standard VSCode setup with the same project open. The team has since made improvements, but it's still significantly heavier. 2. Telemetry Opt-Out Doesn't Work (It Makes It Worse): I found Trae was constantly sending data to ByteDance servers (byteoversea.com). I went into the settings and disabled all telemetry. To my surprise, this didn't stop the traffic. In fact, it increased the frequency of batch data collection. The telemetry "off" switch appears to be purely cosmetic. 3. What's Being Sent: Even with telemetry "disabled," Trae sends detailed payloads including: Hardware specs (CPU, memory, etc.) Persistent user, device, and machine IDs OS version, app language, user name Granular usage data like time-on-ide, window focus state, and active file types. 4. Community Censorship: When I tried to discuss these findings on their official Discord, my posts were deleted and my account was muted for 7 days. It seems words like "track" trigger an automated gag rule, which prevents any real discussion about privacy. I believe developers should be aware of this behavior. The combination of resource drain, non-functional privacy settings, and censorship of technical feedback is a major red flag. The full, detailed analysis with all the evidence (process lists, Fiddler captures, JSON payloads, and screenshots of the Discord moderation) is available at the link. Happy to answer any questions.

Show HN: Ten years of running every day, visualized
839 by friggeri | 427 comments on Hacker News.
Today marks ten years, 3653 consecutive days, of running at least one mile every day under the USRSA rules [1]. To celebrate, I built an interactive dashboard that turns a decade of GPX files into charts you can explore. Running has truly changed my life: I've made lifelong friends, explored beautiful places, and more importantly invested into my own health and fitness, which I'm starting to see the positive benefits as I get older. The stack is pretty simple: a NextJS app, with a Postgres database to keep all my running data, and all the stats are pre-computed and cached in Redis, so I effectively only hit the database once a day when a new run is ingested. On the fronted, I toyed with the idea of using D3 or pre-existing data viz libraries, but ended up rolling my own using SVGs directly, it gave me more control on the visualizations. I used the Strava bulk export to pre-populate the database, and I'm using their webhook API to do incremental updates. I have to tap into OpenWeatherMap and OpenCageDate to enrich the running data a little bit. Happy to answer anything about the stack, data pipeline, or how I stayed motivated for 10 years! [1] https://ift.tt/G4TB3Qu Run Streak Association rules: ≥ 1 mile per day

Pages

Wednesday, 30 July 2025

Tuesday, 29 July 2025

Monday, 28 July 2025

Saturday, 26 July 2025

Thursday, 24 July 2025

Wednesday, 23 July 2025

Tuesday, 22 July 2025

Monday, 21 July 2025

Sunday, 20 July 2025

Thursday, 17 July 2025

Tuesday, 15 July 2025

Monday, 14 July 2025

Sunday, 13 July 2025

Saturday, 12 July 2025

Wednesday, 9 July 2025

Monday, 7 July 2025

Sunday, 6 July 2025

Saturday, 5 July 2025

Friday, 4 July 2025

Thursday, 3 July 2025

Wednesday, 2 July 2025

Tuesday, 1 July 2025