You're being overly modest. You should mention your contributions to the ruby community with respect to Ruby Object Mapper as an example. I have not used it in a project, but in any future undertaking I will most certainly give it a look.
One of the reasons I've started to look more to Elixir and Ecto as ORM is because issues like immutability come up more and more.
In an ideal world we'd have a dynamic client side querying language like GraphQL, a simple application layer that maps REST to CRUD without constraints pushed upon it based on the ORM, and an ORM abstraction that allows for immutability in our models. Concurrency and race conditions are shouldn't be a developers concern when working with higher level framework.
One of the reasons I've started to look more to Elixir and Ecto as ORM is because issues like immutability come up more and more.
In an ideal world we'd have a dynamic client side querying language like GraphQL, a simple application layer that maps REST to CRUD without constraints pushed upon it based on the ORM, and an ORM abstraction that allows for immutability in our models. Concurrency and race conditions are shouldn't be a developers concern when working with higher level framework.