4 ms·
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,
by thegenius2000 11y ago
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/ http://farazdagi.com/blog/2015/vim-as-golang-ide/
- jen20 11y agoI 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.
- jen20 11y agoI 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.