nromito

This is a great explanation of what the intent of GQL is. I'm curious though, as someone who has only a small amount of experience with it, what problem is that solving? From what I can tell, it's the same problem REST solves with a different interface. If it is the over-fetching problem, how big is that problem?

In my experience, it's better to fix a bad endpoint and keep all the browser/server side tooling around tracing requests than to replace all that with a singular graphql endpoint. But curious to hear someone else's opinion here

Location: San Francisco Bay Area

Remote: Yes

Willing to relocate: Want to be in Bay area

Technologies: C, C++, Python, Ruby on Rails, Matlab, OpenCV, git

Resume: http://nickromito.com/

Email: See top of resume