Visual Studio Code is designed to fracture (2022)
Report a link problem
Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderIn some sense, this ought to be an opportunity. VSCode’s ecosystem is, in many respects, quite weak: - cpptools is kind of amazing but also pretty bad. It regularly malfunctions for me. It’s essentially undebuggable. I have less experience with the other extensions, but I don’t expect that they that much better. - The VSCode security story is very, very weak. Extensions are not sandboxed. The client, accessing remote repos, is wildly insecure, by design. And that second point is…
I remember when the FSF had dire warnings about using the Sun JDK. I ignored it and kept on using Java, and nothing bad happened. The JDK was eventually GPLed, and by then I decided I didn't like Java anymore and moved on to better languages anyway. I feel kind of the same about VS Code. Binary product? Telemetry? Centralized marketplace? Some plugins are closed source? Eh, whatever. That stuff doesn't get in my way and I suspect that nothing…
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 671
- Total comments
- 487
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2022-08-31 | Visual Studio Code is designed to fractureFirst breakout | ghuntley | 264 | 142 |
| 2024-01-15 | Visual Studio Code is designed to fracture (2022) | alexzeitler | 2 | 0 |
| 2024-09-29 | Visual Studio Code is designed to fracture (2022)Best thread · Latest 20+ point return | ghuntley | 405 | 345 |