The Franconian
Coder Studio

Why GoLand Remains My Go-To IDE

Why GoLand Remains My Go-To IDE
for Go and TypeScript

After decades of coding and experimenting with various IDEs and editors, I keep returning to GoLand for Go and TypeScript development. Here’s why its features, from code completion to debugging, outshine alternatives like VS Code for my workflow.

The best IDE for my personal daily experience for Go and TypeScript? GoLand, by JetBrains.

When I started playing with code—more than 30 years ago—there were text editors. Happy when they had some code highlighting. My main language was PHP for a long time. Partly Python and Ruby. Almost no Java. And JavaScript. Always tried things like Eclipse or NetBeans. And it began to make more fun.

But the real breakthrough began with PhpStorm. With its release, the whole thing changed for me. While I always tried to work with alternatives like Atom, Brackets, Sublime Text and of course, even vim, I always came back.

Later I switched mainly to Go and was happy when GoLand arrived. But things changed when VS Code evolved and I mainly developed on remote machines. VS Code was great for that.

But GoLand followed suit, and I was back in my favorite environment. And even though I keep trying out alternatives, I always come back. For 2 months I currently used VS Code. It is so great. But still, there are all those tiny things which make GoLand superior for my personal work.

What I missed most with VS Code:

  • The code completion and refactoring features depend on the language server, which is a pain on Windows (very bad performance)
  • Exploring which types implement which interfaces or navigate through this
  • Debugging and running tests—or navigate through results—is clumsy

All those things work. But for me, it’s not enough.

#goland#ide#go#typescript#jetbrains#vs code#development tools