> With Golang, you actually don't need a mega framework to get started You just need to build it from scratch, document it and ensure it is well tried and test

> With Golang, you actually don't need a mega framework to get started You just need to build it from scratch, document it and ensure it is well tried and tested. "mega frameworks" are there for a reason. Rails, Django, Laravel, etc have everything they have because almost any web application you build (except if it is just a minimalist micro-service) will need routing, authentication, i18n, ORM or similar, migrations, caching, e2e testing, validation, background job processing (the one that works after a deploy or restart), and a thousand more other things. Of course you don't need it to "get started", but 1 week after getting started you'll find yourself rebuilding the wheel yourself or tying together 10k dependencies (something doable if you have enough experience and know what to pick and what to not pick, but risky). > And it's not uncommon in Go codebases to repeat yourself. The fact that it is not uncommon doesn't make it any better. Rewriting the universe from scratch in every single project is the worst idea ever. I don't think that because we like a programming language which happens to have no popular web framework we need to negate all the problems of not having one, or say it is in benefit of simplicity. It is not. I'm very sorry for my rant, but I've already faced too many disasters in work environment were people thought that "just flask" would be enough, and years later we're still fighting the fire and trying to understand why this custom ORM validation integration doesn't work.