support for golang on vscode has always been awful and has not gotten any better in any occasion i have tried it out again.

junie actually fixed bugs in my relay code to the point where it's now 100% functional according to mike dilger's relay tester and it's right now being used by dozens of my follows whose clients use outbox model

i have played with cursor a little but aside from looking more impressive than junie, it did very little better in the way of results that i'm not inclined to waste my time with it any further. for now i will put up with junie requiring the use of claude but the moment i can deploy my local LLM on it, will be a very sweet one indeed, because i've got a model now that was trained on Go.

most devs won't even understand why this matters until they dive into Go and discover that most IDEs are shit at go, except for goland. this has not changed in ...7 years. you are a go dev, pretty much if you are serious and do more than just shitty microservices that integrate with shitty mysql and mongo databases, you will not go back once you start using goland.

i can point at many things that annoy me about goland but vscode is unbearable for working with Go code, and i think it reflects in the output of many go devs who use vscode, what a fucking shitshow their codebases are