[diehunde]

Yeah but a lot of prototypes will have similar requirements. Let's say I need to build an app I already know will need to route requests, authentication, versioning, some sort of sql layer to not write SQL code, etc. I don't see a problem with starting with a framework for that. I'm new to Go so maybe all of that it's extremely easy to do without any library, in which case I would be wrong.

[_y5hn]

How do you know exactly the implementation of all that, or wether there's simpler alternatives for your chosen bounded context? It's not just a Go thing, though the language promotes using stdlib more and external dependencies less, starting small and build from there. If you were to use a particular gaming engine or web framework, sure, but then again unless you know Go to be a great fit, or built by you to be great, why use Go at that stage. How would you know beforehand?

It's not so much writing the code, that's the easy part, but reading and tweaking it later and not go hmm..

There something to smaller, simpler and btw, nobody is saying golang is currently a good fit for all kinds of projects, but the core ideas are easy for new developers and interesting for experienced ones.

Composing smaller components into a bigger system would be a great fit, and it could also be used for a monolith, though golang really shines most where code is segmented into clever little independent features. This may require some extra design and systems thinking.