I did search too and all I found were comparisons to REST .. well, from
what I can tell, GraphQL is a data format as well as a way to use a generic
endpoint (ie, the endpoint/request is in the data). and they say "it's
easier to use and your colleagues down the road will appreciate it!" But
you're still making a request to a generic endpoint!

I bet if we searched back in 2010 why to use JSON instead of XML we'd get
the same answer. And back in 2000 why to use XML vs X.12, the same thing.

Again, it's ridiculous. Is IBM going to now start adding that into their
APIs/%bifs/SQL to build/parse as well? I know when they started doing it
with XML I could see and did say "it's going to change soon.. like it
always does..." And it did. And now this. Not saying IBM isn't helpful,
just saying we always seem to be 4-5 years behind, and without enough ISVs
or Open Source folks to help, falling behind again.

I was so excited to see this endpoint move away from having to use their
SDKs... but I see it was one step forward (ie, we can make simple web
requests instead of needing to use their SDK with Node, etc), but 2 steps
back (they could have used JSON, but decided to mix JSON and GraphQL).

So it may be something that will still require more backend OSS processes
that are needed to build and/or process the data... All because you took
JSON and removed some delimiters (commas mainly) from it and called it
something else.. haha..

The request I posted as an example would be such a more simple request if
it was made to a specific endpoint with just JSON. Or even a generic
endpoint with a descriptor in the JSON on what the request is.

It's similar to the gripe I have with requests that use data in the URI
path... no, just pass the data in the body, or even as a query string...
why make things so difficult and different every 5 years.

What are they teaching in comp sci these days? Oh ya.. job security. :)

Ok, hopefully I'm done with my rant. haha.

On Tue, Oct 19, 2021 at 11:59 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

If you check the web Brad you'll see there are a few discussions on the
topic. Not sure I understood the responses but ...


Jon

On Oct 19, 2021, at 12:52 PM, Brad Stone <bvstone@xxxxxxxxx> wrote:

No thanks, Matt. :)

I'm still curious as to WHY... why not just use JSON? What makes GraphQL
better? And if it's better, why wrap it in JSON?

It's getting a little ridiculous.

On Tue, Oct 19, 2021 at 11:41 AM Matt Olson via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I've heard .net can run on the IBMi (not sure why you'd want to though,
could instead use a commodity windows server), and there's a heavily
used
.NET GraphQL library out there to make interacting with GraphQL
endpoints
easy:


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.