Huh? https://github.com/derekparker/delve integrates nicely with many editors, including [1] and [2] and allows you to do exactly that.
1 - https://www.jetbrains.com/go
2 - https://github.com/Microsoft/vscode-go
In Nine years of Gomicrosoft
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
23Distinct people
28Mentions
0Explicit recommenders
5.9KGitHub stars
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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:23:53 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 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
| 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 GitHubWhat Hacker News says
5 sourcesI personally almost never use a debugger with Go (or Rust), but it looks like you can get all of that functionality with VS Code using Delve: https://github.com/Microsoft/vscode-go/wiki/Debugging-Go-cod...
I found a video of someone debugging Go code in VS Code, and I saw them set breakpoints, step around in a function, and hover over a variable to see its value, in addition to the sidebar containing all of the values of all of the local variables and the stack traces.
In Nine years of Go>We are OK with using dep, definitely miss a debugger or an REPL.
I personally use Visual Studio with the go extension and delve and the debugger works quite well.[1]
I believe that the Goland IDE also has an integrated debugger.[2]
[1] https://github.com/Microsoft/vscode-go/wiki/Debugging-Go-cod...
[2] https://www.jetbrains.com/go/features/
In Nine years of GoVSCode-Go now supports go modules
1 points · Open discussionHave you looked at golangci-linter [1] at all? It's a competing project that also implement a bunch of linter rules, and was created because gometalinter is too slow.
One reason golangci-linter is faster is that it shares the same in-memory representation of the linted packages between all the linters. From what I can tell, Revive requires that each rule parse the file itself, which is the same design gometalinter use, and it will absolutely kill performance for anything that needs to operate on the full AST.
Also, the Go community does not need a bunch of competing linter tools. For one, at means that tools like Visual Studio Code's Go plugin [2] will have to build special support for each linter tool. Gometalinter was nice because it built lots of rules (including golint) into a single tool, so you just needed that one tool.
I agree wit
Read the rest
h the others about configuration. I think a lint tool should have a configuration work out of the box that reflects Go standards that everyone, without doubt, uses. More controversial conventions such as requiring all exported functions to have comments don't need to be included.
[1] https://github.com/golangci/golangci-lint
[2] https://github.com/Microsoft/vscode-go