3 ms·
I use primarily JetBrains IDEs (namely WebStorm and Goland). For Go, it’s unsurpassed. The refactoring are generally smarter than what’s implemented in gopls (w
by travisd 5y ago
I use primarily JetBrains IDEs (namely WebStorm and Goland). For Go, it’s unsurpassed. The refactoring are generally smarter than what’s implemented in gopls (which is the language server that VSCode uses). For example, catching the common “assert implements interface” (var _ interfacetype = concretetype) idiom and offering to stub out the missing methods.
They recently launched some remote dev tools (mentioned in the post), but they’re very sensitive to network latency since it’s essentially (afaict) just forwarding the window (the whole IDE has to be installed on the remote server). VSCode far surpasses this for me (essentially just tunneling the file system operations and terminals). Doing Linux specific dev work from my MacBook, VSCode is my go to.
- denysvitali 5y agoI personally use Goland for Go and Rust. Until a couple of months ago (during the Advent of Code) I was under the assumption that you can use the debugger with Rust only in CLion. Apparently this changed and I can simply pay for Goland (awesome IDE!) instead of Goland + CLion Debugging Rust on Goland, compared to VSCode is way better. Not only because of the debugger UX, but also because Goland as an IDE for Rust (code completion, types recognition and speed) is miles ahead of VSCode (despite I think they use the same backend).