Hacker News new | ask | show | jobs
by iaaan 524 days ago
I recently had to switch from Jetbrains to VSCode for Go development and it took days of troubleshooting to get the debugger working. I don't even remember what the problem ended up being offhand.

And that's in addition to having to acclimate myself to completely different and objectively worse syntax highlighting (you can customize the colors of more types of tokens using Jetbrains syntax highlighting system), worse global find+replace, and losing all Intellisense features (hovering on types, ctrl+click to type definitions, etc.) whenever there is a syntax error anywhere in the entire repo.

1 comments

I write in Go in IntelliJ full-time, do I miss any features from VSCode? Why did you move?
Nope. We were forced to by management.