blog/go-dev-environment-vscode-wsl/ #1199
Replies: 2 comments 1 reply
-
Want to join in the discussion? You can do that in two ways! You can either authorize the giscus app to post on your behalf using the GitHub OAuth flow. Alternatively, you can comment in GitHub Discussions directly if you'd prefer not to grant access to the giscus app. Please keep the discussion on topic with the post. |
Beta Was this translation helpful? Give feedback.
0 replies
-
"Go (commonly referred to as goland)" should read "Go (commonly referred to as golang)" |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
blog/go-dev-environment-vscode-wsl/
Over the past few weeks, I have been working on a new set of pet projects. I've wanted to learn Go for a while, so I thought this could be a great opportunity to get hands on and try it out. It's fair to say that my development environment was 'functional', but I wanted to revisit it to make sure that I could get the best out of it. In this blog post, I'm going to walkthrough the process of setting up Go on my machine, and then the experience of using Visual Studio Code and Windows Subsystem for Linux (WSL) with Ubuntu.
https://www.cloudwithchris.com/blog/go-dev-environment-vscode-wsl/
Beta Was this translation helpful? Give feedback.
All reactions