4 ms·

Thanks. How about a framework which has all these things stitched together already? For example, a good templating engine and an ORM that supports DB migrations

• pphysch 5y ago
  GORM (https://gorm.io/index.html https://gorm.io/index.html) has auto migrations. But it is still a framework, which means it is making a lot of decisions for you and forcing you to learn its own way of doing things. Ultimately it is a relatively thin layer over builtin Go libraries like `html/template`, `net/http`, `database/sql`; generally speaking, the Go philosophy is to build systems yourself from these components and therefore keep the architecture simple, focused, and maintainable. Unless you are stuck with Go for a good reason, if you want a framework use one of the industry standard ones mentioned previously.