3 ms·
I've worked with SAP way too much - it's at least as horrible as you imply. But I've also worked with both OData and GraphQL at lot, and I don't understand you
by GordonS 7y ago
I've worked with SAP way too much - it's at least as horrible as you imply.
But I've also worked with both OData and GraphQL at lot, and I don't understand your beef with OData, and certainly don't get your claim that it's more complex than GrahpQL. IMO, OData is quite a lot simpler than GraphQL, and I actually prefer it.
- zxienin 7y agowhere is GraphQL v/s OData above?
- GordonS 7y agoNot sure if I've misinterpreted your comment then? The GP asked if these were GraphQL APIs, then you said: "OData. That’ll surely take them far within developers. Maybe SAP brainwashed devs, who are willing to bear any level complexity SAP throws out" and also: "Why position “zero SAP knowledge required” and then throw odata in?"
- zxienin 7y agocan't seem to reply to your comment below (no 'Reply' option for me, likely HN feature to avoid too deep nested threads) > Not sure if I've misinterpreted your comment then? Yes, misinterpreted. Refer: https://news.ycombinator.com/item?id=22807146 https://news.ycombinator.com/item?id=22807146
- GordonS 7y agoSorry, but I still don't get what you're trying to say - I've read the comment you linked to, and I understand it as an implication that OData is problematic somehow. In another comment in reponse to someone complaining about OData, you also said: "Had the same sentiments. They take good step forward and then chose OData (bummer)" Stil scratching my head about what I'm misinterpreting here.