Yes. Nothing fancy from workflow. I pay for and use Goland because I find it so good for refactoring... worth the expense over VSCode.

Generally I use standard library, with the exception being github.com/gorilla/mux Gorilla Mux for routing because it removes so much boilerplate.

I do however use Python for all HTTP integration tests. With requests + voluptuous its so much more productive than doing them in Go, which I had previously done.

How do you access your database? How do you do migrations? How do you do end to end testing? How do you do fixtures? How do you do user input validations and error reporting? How do you do translations and 18n in general? Do you have any kind of admin ui? How do you handle assets? How do you do ajax calls? How do you send emails? How do you handle general error reporting to sentry, or similar?

Go is great for systems programing, building kubernetes, CLIs, etc.

It is very far from being a good idea to use it for general web development. Right tool for the job and such.

Go is also great for building performant APIs (REST or RPC).

I agree is not ideal if you want a full-blown monolith web app. In that case a typical MVC framework will save you weeks.

I agree only in that it is performant, but from a purely computational point of view.

Even if it is just a rest api, you still need a database/ORM layer, a validation framework, a migrations system, a way to document it, etc.

So, from a developers life quality and company economics point of view, django or rails are way, way more performant, but not as cool I agree.

Sure, if you're building Facebook or google Go might be the best option.

All of that is already built via libraries. Talking about facebook, they released an ORM a a while ago[1] and it has support for all the things you mention.

[1] https://github.com/ent/ent