Not all ORMs are like hibernate and gorm.
I'm author of a lightweight ORM for Go and Scylla / Cassandra [1] so I may be biased.
In my view use of a good ORM makes your code more resilient to change, refactorings are simple and stupid mistakes largely eliminated.
A benchmark of usefulness of an ORM can be how many lines need to be changed to add a new field to a struct / class.
In a good ORM this should be about 1, it should still work be ~1 if you use a hand crafted SQL / CQL.
The worst thing that ORMs try to do is handling relations (eager / lazy loading) and handling sessions / object lifetime. This is mainly because it's impossible to have one-fit-all solution for all usecases even in one application.