And there alternatives. The best known is probably Revel: https://revel.github.io
For a doctrine (ORM) alternative you have for example https://github.com/jinzhu/gorm
The point about Go; using those types of tools is generally frowned upon in the community. It's overkill for most (micro)services.
But few gophers build a full-stack website in a single application.
I'm a gopher; I wouldn't want to use Revel or Gorm. I feel I'd be using the wrong tool for the job. I'd more likely use Django or Symfony when I'd need to build a full-stack SSR.
If a backend API is used by different clients (mobile apps, SPA, servers, ...) using a full-stack SSR framework like Symfony or Django doesn't make much sense anymore. You wouldn't use 90% of the framework's features. It feels like bloat.
But many websites don't need to serve different clients.
The author's decision to go from Golang to PHP makes perfect sense if he's building SSR websites.
I'm getting old ;)
Obviously things will have matured since then.
Doctrine implements the Unit of Work pattern. From what you're saying GORM is more like an Active Record ORM.
You're right, that wouldn't make it a good direct alternative.