rj5
Re:Scaling to 1M active GraphQL subscriptions on Postgres
on Wednesday June 12, 2019 @08:34PM (#20170806)
I can’t wait to try this out!
Re:Desktop Neo – rethinking the desktop interface for productivity
on Wednesday June 12, 2019 @08:25PM (#20170754)
This looks really good! I’m curious how good the eye tracking works in practice though.
Re:Show HN: Hack – new Hacker News iOS client with swipe to upvote, fa...
on Thursday May 23, 2019 @10:52PM (#19998072)
Nice!
Re:The Mysterious History of the MIT Licensed
on Sunday April 28, 2019 @04:55AM (#19770092)
Fascinating Article!
Re:Heathrow Airport remove need for passports with new facial recognition
on Saturday April 27, 2019 @09:09PM (#19768677)
It’s about time!
Re:The Terrifying Potential of 5G
on Saturday April 27, 2019 @09:08PM (#19768671)
Agreed!
Re:Graphiti: Stylish Graph APIs
on Thursday April 25, 2019 @12:47PM (#19749952)
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.
Re:Graphiti: Stylish Graph APIs
on Tuesday April 23, 2019 @03:22PM (#19731954)
I've used Graphiti in a project; as it looked promising on the surface. But as my needs grew, I often found myself fighting with the DSL. It makes the easy things easy, and the hard things very painful and hard. This is a problem with any DSL heavy framework.
If you have a toy project, than try Graphiti. If you're solving real-world problems; stick with GraphQL.