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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 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

89 sources
To elaborate in more (possibly excruciating) detail: It's very rare for anyone on GitHub to do the sort of tiered collaboration that the Linux kernel uses. If, say, I want to contribute to VSCode, pretty much the only way to get my changes upstream is to submit pull requests directly to github.com/Microsoft/vscode. Compare to the tiered approach, where I notice someone is an active and "trusted" contributor, so I submit my changes to their fork, they accept them, and then those changes eventually make their way into the canonical repo at some future merge point. That's virtually unheard of on GitHub, but it's the way the Linux kernel works. Pretty much the only way you could get away with something even remotely similar and not have people look at you funny in the GitHub community is maybe if you stalked someone's fork, noticed they wer
Read the rest
e working on a certain feature, then noticed there was some bug or deficiency in their topic branch, then they wake up in the morning to a request for review from you regarding the fix. Even that, which would be very unusual, would really only work in a limited set of cases where you're collaborating on something they've already undertaken—there's not really a clean way in the social climate surrounding GitHub to submit your own, unrelated work to that person (e.g., because it's something you think they'd be interested in), get them to pull from you, and then get upstream to eventually pull from that person.
In Microsoft and GitHub team up to take Git virtual file system to macOS, Linux
> "where's the in-editor JS REPL" Can use Code Runner for evaluating JS in a REPL... https://marketplace.visualstudio.com/items?itemName=formulah... Can also use the Shell Arguments feature of the Integrated Terminal to start up a JS REPL when opening a new terminal window... https://code.visualstudio.com/docs/editor/integrated-termina... > "there doesn't seem to be any way to have system-specific configs" Just use Git, and only clone the repos for the system settings you're interested in using. So, if you have a Git repo for VS Code settings on PC 1, don't clone it on PC 2. Not that hard is it. > "And I'm not going to mention org-mode." I think you just did. It looks like someone wanted to implement it in VS Code ( https://github.com/jsonreeder/vscode-org-mode ) but there were issues holding it back from being implemented fully, such as:
Read the rest
In 10 years of love for Emacs undone by a week of VSCode
The problem with `cmdline` modes is definitely that tab completion doesn't work imo. Unluckily, that's blocked on the VSCode side, although it is possible to move our cmdline down to the status bar (probably would have been the better choice to begin with, really). For example, with the neovim rewrite it's possible to expose not only tab completion, but also the wildmenu: https://imgur.com/DO6IXYb If we wanted to keep it in the input box that pops up, we would need something along these lines: https://github.com/Microsoft/vscode/pull/36690 (it is my PR, for disclosure).
In VS Code Roadmap 2018
> but it sends data to Microsoft even with Telemetry et al off I think Microsoft responded 100% correctly. They stated what they were doing, proved what they did, and they were wrong and stopping it. BTW I rather deal with a developer that is that responds this way. I also don't mind my editor sending update pings and when I have crashes which most programs are opt-out. From 2016 > today we continue to send events stating that a user has opted out and nothing else i.e. no usage data is sent. Here is the test to ensure that is all we send... https://github.com/Microsoft/vscode/blob/master/src/vs/platf... But we don’t need to do that and I don’t think it’s what you expect as a user – so we will stop sending anything i.e. even the opt out event Look for a change there soon. Thanks for bringing this to our attention and I hope you enjoy work
Read the rest
ing with VS Code.
In VS Code Roadmap 2018
I really want to try VSCode, but it sends data to Microsoft even with Telemetry et al off [1]. Which is not surprising considering that Windows itself does the same thing [2] (hence, my not using Windows). Even if they allowed us to opt-out of telemetry now, I wouldn't trust them not to silently opt us back in later. This is not something I can accept my editor doing, and would expect a little less apathy about it from the HN crowd. Does anyone know more about the MS spyware and how much I need to worry about it? [1] https://github.com/Microsoft/vscode/issues/16131 [2] https://arstechnica.com/information-technology/2015/08/even-...
In VS Code Roadmap 2018

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