Maybe it’s just me, but having used both tools; graphQL-ruby is much simpler. There isn’t much to learn with graphQL-ruby, since the graphql spec is so elegant compared to jsonapi.
Fighting with the DSL, I mean cryptic errors, no instance variables to work with, and no straight forward way to extend the framework. I know it is possible to extend the framework, but it’s not very intuitive.
To add on to this, we'd love to get specific examples of things that you find challenging or that otherwise don't work well. We've found over time that these tend to fall into either A) a missing feature, B) Missing documentation, or C) a missing concept in the domain being modeled. As we've added more features and handled the edge cases, we see more of B & C than A, but of course that happens still as well.
Fighting with the DSL, I mean cryptic errors, no instance variables to work with, and no straight forward way to extend the framework. I know it is possible to extend the framework, but it’s not very intuitive.