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

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:17:07 AM 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

60 sources
Our algorithm gives lots of credit to removing old lines of code! But to your broader point, I think there certainly is information about effort at the code level. Consider for example these two PRs: https://github.com/PostHog/posthog/pull/23858 and https://github.com/microsoft/vscode/pull/209557. It's pretty easy to tell which one was more effort even if you don't know anything about the process for how they were implemented. Do you have any shareable examples you want me to test out? Or of course you can try it yourself :)
In Show HN: Weave - actually measure engineering productivity
Our metric is approximately "hours of work for an expert engineer." Here are some example open source PRs and their output metrics calculated by our algorithm: https://github.com/PostHog/posthog/pull/25056: 15.266 (Adds backend, frontend, and tests for a new feature) https://github.com/microsoft/vscode/pull/222315: 8.401 (Refactors code to use a new service and adds new tests) https://github.com/facebook/react/pull/27977: 5.787 (Small change with extensive, high effort tests; approximately 1 day of work for expert engineer) https://github.com/microsoft/vscode/pull/213262: 1.06 (Mostly straightforward refactor; well under 1 day of work)
In Show HN: Weave - actually measure engineering productivity
Jetbrains will automatically warn you if your package.json is ever out of sync with the actual installed packages (a little dialog pops up). It's not clear to me how VScode handles this (and in fact, one of my colleagues often struggled with this). Closed issue with unclear resolution: https://github.com/microsoft/vscode/issues/66288 It's one of the many, many, many nice little touches that Jetbrains offers over VScode, and I heavily recommend people who have never tried it to give it a shot for a few weeks/months. It's a LOT better than vanilla VSCode, and slightly better than VSCode + a ton of third-party extensions. -------- Beyond that, I also see npm script chaining. e.g. instead of `npm run dev` to start your server, `npm run pre-dev-scripts` which call a bunch of other updates, style token generations, npm install, whatever. Combin
Read the rest
e that with git hooks (like pre-commit linting & formatting) and it's often pretty automatic. For external services, you should be able to specify them in some IDE config file that can trigger task runners, monitors, etc. and share that in the repo with your teammates: https://code.visualstudio.com/docs/editor/tasks That's a bit harder if you work across IDEs (like VScode and Jetbrains), but not always impossible. Our Docker auto-updates in VScode, for example, but doesn't do anything in Jetbrains :(
In Ask HN: How do you keep track of actions to perform at next pull?
For what it's worth; Visual Studio Code and VSCode are not the same. VSCode is MIT licensed: https://github.com/microsoft/vscode/blob/main/LICENSE.txt From vscodium.com: Microsoft’s vscode source code is open source (MIT-licensed), but the product available for download (Visual Studio Code) is licensed under this not-FLOSS license and contains telemetry/tracking. According to this comment from a Visual Studio Code maintainer: When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license. When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a “clean”
Read the rest
build, without the Microsoft customizations, which is by default licensed under the MIT license The VSCodium project exists so that you don’t have to download+build from source. [VSCodium] includes special build scripts that clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries for you to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.
In SSH Remoting
> VSCode is provided fully free as in beer and freedom No, VSCode is a proprietary text editor/IDE from Microsoft. Code-OSS is provided fully free as in beer and freedom, and is currently what resides at https://github.com/microsoft/vscode. Why would Microsoft not want other AI agent extensions to get the same benefits, which would benefit all AI agent users? Edit: I have removed the portion of the comment which discussed the throwaway account.
In Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?

Showing the 15 most recent of 60 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.