5 ms·

Wow, I did not expect that. I'm currently using VS Code for Go and I'm pretty happy with it. Definitively gonna try this out because I'm pretty much using JetBr

Wow, I did not expect that. I'm currently using VS Code for Go and I'm pretty happy with it. Definitively gonna try this out because I'm pretty much using JetBrains for everything else and never got disappointed by them yet.

devoply 10y ago
VS Code is awesome for Go. If you are doing Go and not using it, you should!
- IshKebab 10y ago
  I also like LiteIDE.
  - commentzorro 10y ago
    Me too. Very lightweight and fast. Don't know why it doesn't get more love?
- laumars 10y ago
  > If you are doing Go and not using it, you should! That's a very assertive statement to make about something that's completely preferential. For what it's worth, I tried VSC but really didn't like it. Partly because the whole Electron thing made it run like crap on modest hardware with lots of other stuff running. And partly because I didn't much like the defaults (font sizes, layout, etc). The latter could all be "fixed" to my preferences but IntelliJ and Sublime Text - both with their respective Go plugins - were already better aligned to my workflow so I saw little point wasting time on yet another "text editor with knobs on".
wtf_is_up 10y ago
IntelliJ IDEA has a Go plugin that works very well. I've switched from Sublime -> VSCode -> IntelliJ for my Go development and I haven't looked back.
- ben_bai 10y ago
  Not for long, if this catches on. There was a free C plugin, now you have to pay for CLion.
  - AsyncAwait 10y ago
    To be fair, CLion is much more full featured than the C plugin was.
- thiht 10y ago
  I started using Intellij's plugin for Go development but the debugger just didn't work (well... it worked once per OS boot) VSCode's debugger worked well in the early stages of Go which why my team and I switched to it and sticked with it. VSCode is pretty awesome and, we believe, better than Intellij's unofficial plugin. I'm really excited by Gogland though
chrisper 10y ago
While I liked it, it was quite buggy for debugging. I hope Gogland is better.
- AsyncAwait 10y ago
  They specifically mention improving the debugging experience: https://www.jetbrains.com/help/go/1.0/faq.html#d3e52 https://www.jetbrains.com/help/go/1.0/faq.html#d3e52

devoply 10y ago

VS Code is awesome for Go. If you are doing Go and not using it, you should!

IshKebab 10y ago
I also like LiteIDE.
- commentzorro 10y ago
  Me too. Very lightweight and fast. Don't know why it doesn't get more love?
laumars 10y ago
> If you are doing Go and not using it, you should! That's a very assertive statement to make about something that's completely preferential. For what it's worth, I tried VSC but really didn't like it. Partly because the whole Electron thing made it run like crap on modest hardware with lots of other stuff running. And partly because I didn't much like the defaults (font sizes, layout, etc). The latter could all be "fixed" to my preferences but IntelliJ and Sublime Text - both with their respective Go plugins - were already better aligned to my workflow so I saw little point wasting time on yet another "text editor with knobs on".

wtf_is_up 10y ago

IntelliJ IDEA has a Go plugin that works very well. I've switched from Sublime -> VSCode -> IntelliJ for my Go development and I haven't looked back.

ben_bai 10y ago
Not for long, if this catches on. There was a free C plugin, now you have to pay for CLion.
- AsyncAwait 10y ago
  To be fair, CLion is much more full featured than the C plugin was.
thiht 10y ago
I started using Intellij's plugin for Go development but the debugger just didn't work (well... it worked once per OS boot) VSCode's debugger worked well in the early stages of Go which why my team and I switched to it and sticked with it. VSCode is pretty awesome and, we believe, better than Intellij's unofficial plugin. I'm really excited by Gogland though

chrisper 10y ago

While I liked it, it was quite buggy for debugging. I hope Gogland is better.

AsyncAwait 10y ago
They specifically mention improving the debugging experience: https://www.jetbrains.com/help/go/1.0/faq.html#d3e52 https://www.jetbrains.com/help/go/1.0/faq.html#d3e52