News for hackers. Stuff that matters.
Re:You Might Not Need GraphQL by aryes on Wednesday April 12, 2017 @06:16PM (#14102241)
No the article is right OData offers most of what graphQL has now since 2012. Honestly aside of the HATEOAS principle (see ion).

But the key difference is the community engagement and corporate sponsorship, OData had only a lukewarm support from Microsoft and others like SAP. And aside Apache Olingo there isn't much left in library support. (Trust me I'm sad to have to write this).

GraphQL on the other hand is drawing both community and corporate support including full support from FB. Time will tell if this will diminish, but the support seems to mimick the success with golang.

Re:You Might Not Need GraphQL by techniq on Friday April 14, 2017 @10:57AM (#14114812)
I've created a lightweight odata query builder based somewhat on MongoDB and js-data's query object syntax you might find helpful: https://github.com/techniq/odata-query

I also built a React component that builds upon this as well, if you're into that - https://github.com/techniq/react-odata

Re:You Might Not Need GraphQL by int_19h on Wednesday April 12, 2017 @06:48PM (#14102462)
And speaking of OData, is there any good side by side comparison of OData and GraphQL?
Re:You Might Not Need GraphQL by aryes on Wednesday April 12, 2017 @07:38PM (#14102756)
Re:You Might Not Need GraphQL by int_19h on Wednesday April 12, 2017 @06:46PM (#14102441)
Microsoft essentially created OData; what do you mean by "lukewarm support"?
Re:You Might Not Need GraphQL by aryes on Wednesday April 12, 2017 @07:23PM (#14102669)
Lukewarm relative to the support FB is giving to graphQL. To me opendata felt like a second class project (vs the efforts MS has put around .Net and other code that was open sourced recently). But it may just my perception.