microsoft

vscode-go

TypeScript2015–2020

microsoft / vscode-go · Archived

vscode-go

An extension for VS Code which provides support for the Go language. We have moved to https://github.com/golang/vscode-go

Developer Tools

Explore on GitHub Read Hacker News discussions

23Distinct people

28Mentions

0Explicit recommenders

5.9KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

An extension for VS Code which provides support for the Go language. We have moved to https://github.com/golang/vscode-go

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

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

Also in these discussions

derekparker/delve · linked in 2 of the same discussions
golang/go · linked in 2 of the same discussions
microsoft/vscode · linked in 2 of the same 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:59:53 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 year28 dated mentions

Observed mentions: 2015-11-18 16:33:11 UTC to 2020-04-14 21:32:01 UTC.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	2	0	2
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	11	2	9
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	3	0	3
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	5	1	4
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	4	0	4
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	3	0	3

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction

Go for Visual Studio Code An extension for VS Code which provides support for the Go language. We have moved! 🏡 🚚 🏡 As of June 2020, our new home is https://github.com/golang/vscode-go. For more on this, please see the below blog posts The next phase of Go experience in VS Code VS Code Go extension joins the Go project Contributing This project welcomes contributions and suggestions. Please go through the Contributing Guide in the new repository. Code of Conduct This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments. License MIT

Read the full README on GitHub

What Hacker News says

4 sources

georgewfraser·Dec 1, 2019

The most obvious application of tree-sitter is editors. I wrote a VSCode extension to replace the built-in syntax coloring with tree-sitter-based coloring: https://marketplace.visualstudio.com/items?itemName=georgewf... I actually think it would make more sense for the various VSCode language extensions to just bake in tree-sitter for their language. I have had a PR open to do this with golang for a while: https://github.com/microsoft/vscode-go/pull/2555

In Tree-sitter: new incremental parsing system for programming tools (2018) [video]

int_19h·Apr 10, 2019

Most Microsoft VSCode plugins are open source. If you click on details in the extension marketplace, you'll see a lot of GitHub URLs: https://marketplace.visualstudio.com/publishers/Microsoft And perhaps most ironically in this context: https://github.com/Microsoft/vscode-go

In Google releases closed source VS Code plugin

shawnz·Mar 20, 2019

It's not a python problem. Like I said, when you initiate a debug session, VS code will launch the python binary just fine, but it passes it the Windows path of the file you're debugging which obviously the WSL python binary can not understand. I assume F# on WSL would have the same issue, although I haven't tried personally. Here you can see a bug report for the issue: https://github.com/Microsoft/vscode-python/issues/67 And the same issue for other languages: https://github.com/Microsoft/vscode/issues/22663 https://github.com/Microsoft/vscode-go/issues/926 Looks like they've implemented fixes for C++ and nodejs though: https://github.com/Microsoft/vscode-cpptools/issues/85#issue... https://github.com/Microsoft/vscode/issues/39144#issuecommen...

In Is WSL actually ready for developers?

kyrra·Mar 20, 2019

The VSCode go plugin team has been doing a good job of staying on-top of this[0]. Which points to a golang bug[1] where the Go team is tracking tooling programs that need to be updated for Go Modules. So the Go team is aware of this issue and people are working to get all the major tools on board. [0] https://github.com/Microsoft/vscode-go/wiki/Go-modules-suppo... [1] https://github.com/golang/go/issues/24661

In Using Go Modules