News for hackers. Stuff that matters.
Re:Project Rider – A C# IDE by 0xFFC on Wednesday January 13, 2016 @08:21AM (#10894033)
A full Go ide would have been better in my experience.
Re:Project Rider – A C# IDE by winterbe on Wednesday January 13, 2016 @10:00AM (#10894729)
2 jetbrains devs work full time on a Go plugin for Intellij: https://github.com/go-lang-plugin-org/go-lang-idea-plugin
Re:Project Rider – A C# IDE by 0xFFC on Wednesday January 13, 2016 @10:31AM (#10894973)
Cool, This is what I am talking about, This could end up very well. But they should put "Official" tag on it. Good job Jetbrain.
Re:Project Rider – A C# IDE by jen20 on Wednesday January 13, 2016 @08:26AM (#10894062)
I switch between Emacs and IntelliJ's Go plugin for working on Terraform - the Go plugin is very complete, and as far as I'm aware the only working visual debugger for Go.
Re:Project Rider – A C# IDE by Vendan on Wednesday January 13, 2016 @09:00AM (#10894259)
Check out LiteIDE, it's got visual debugging support as well.
Re:Project Rider – A C# IDE by StevePerkins on Wednesday January 13, 2016 @08:48AM (#10894179)
Genuinely curious... what would you like to see in a Go IDE that isn't provided for free by IntelliJ Community Edition and the Go plugin today?
Re:Project Rider – A C# IDE by 0xFFC on Wednesday January 13, 2016 @09:52AM (#10894654)
Official support ?
Re:Project Rider – A C# IDE by thegenius2000 on Wednesday January 13, 2016 @09:00AM (#10894255)
You should also consider vim (w. the vim-go plugin) if you're on Unix.

It's well-written, and along with several other vim plugins and a decent configuration, it's miles ahead of any IDE (except emacs, not starting an editor war here).

Read here, http://farazdagi.com/blog/2015/vim-as-golang-ide/

Re:Project Rider – A C# IDE by jen20 on Wednesday January 13, 2016 @11:21PM (#10899617)
I have found that vim-go is effectively unusable if you are editing files over a few hundred lines long or on large projects. The time between :w and regaining control of the editor is just too long. Much of this is probably due to the execution time of the compiler for Syntactic checking, and has extended significantly in Go 1.5.

Colleagues tell me that neovim alleviates some of this, but during the time before that was stable I switched to emacs (specifically Spacemacs) with evil mode instead.