HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
microsoft
vscode
TypeScript2015–2026
microsoft / vscode

vscode

Visual Studio Code

Developer ToolsWeb DevelopmentMobile & Desktop
Explore on GitHubRead Hacker News discussions
573Distinct people
730Mentions
8Explicit recommenders
195.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Visual Studio Code

GitHub

Where it is used

  • OWASP cve-lite-cli (examples / case studies) — The OWASP cve-lite-cli repository (examples/readme.md) includes an explicit in-repo snapshot/case study that names microsoft/vscode and describes scanning its root lockfile as an example dataset. Source

What people are saying

My favorite new CSS feature is the Custom Highlight API, which allows you to style arbitrary (and potentially overlapping!) text ranges without needing to create ad hoc <span>…

aragonite used a recommendation phrase. 9 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year730 dated mentions

Observed mentions: 2015-11-18 15:52:45 UTC to 2026-10-30 18:10:55 UTC.

0204060801002015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 77 mentions; 3 submissions, 74 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 89 mentions; 16 submissions, 73 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 67 mentions; 9 submissions, 58 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 55 mentions; 11 submissions, 44 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 74 mentions; 13 submissions, 61 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 67 mentions; 8 submissions, 59 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 49 mentions; 8 submissions, 41 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 67 mentions; 15 submissions, 52 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 60 mentions; 15 submissions, 45 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 59 mentions; 14 submissions, 45 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 59 mentions; 16 submissions, 43 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC725
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC77374
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC891673
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC67958
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC551144
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC741361
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC67859
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC49841
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC671552
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC601545
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC591445
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC591643

What Hacker News says

730 sources
potamic·Oct 16, 2026
It's perhaps a good time to bring attention to this open issue [1] on vscode from 2015 with thousands of upvotes, hundreds of comments pleading, the collective hive mind losing their minds over how a usability requirement so basic can be left neglected for years altogether even as so many other not so requested features seem to have no problem getting piled on. While this issue has been a personal pain point, I do recall there were quite a few widely requested usability issues that went unaddressed over the years. So I'm not sure about how to react when I read this blog post about "modernizing" vscode UI in 2026. How can you talk about modernizing and journey through a 5-stage evolution when fundamental aspects are so obviously unaddressed? What is a modern UI anyways and how is it better than ancient UI? What specific advancements in HCI
Read the rest
research from the last 10 years are being incorporated here to call the UI modernized? I have to take a dig at the larger design community because I think this is not an isolated problem. Software usability in general has been going down for me over the years. There was a time when you would hear more from the community about the science of interaction and why you would design an interface in a certain way. Of late I feel the emphasis shifting more towards visual design with things like colors, spacing, border radii etc. with this blog post being a case in point. If HN were to be launched today, I'm sure it would look nothing like what it does and instead have a more "modern" UI. But, would it be an improvement? [1] https://github.com/microsoft/vscode/issues/519
In Modernizing the VS Code UI
gpugreg·Sep 14, 2026
I stopped using GitHub Copilot extension in VS Code when they introduced their new pricing model, but I should have switched much earlier. The developers have barely a clue how LLMs work and the company structure is misaligned with creating a quality product. They do not perform benchmarks to evaluate whether new "features" are any good and instead bloat the context with more and more tools that are rarely useful and often confuse models. Eventually, the context window got so bloated that they resorted to hiding function bodies in large files, which is of course a stupid idea because then the LLMs have to use other tools to read the files, wasting even more tokens, or hallucinate the content. Honestly, it is amazing that LLMs work at all in VS Code. You can inspect the context by pressing F1 and then selecting "Developer: Show Chat Debug
Read the rest
View" in VS Code (https://github.com/microsoft/vscode/wiki/Copilot-Issues) and marvel at all the garbage that is in there.
In Notes on gotchas while migrating 35kb preprompts from Opus to self-hosted Ollama

Showing the 15 most recent of 730 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.