I have a backend generator that also generates typescript and dart models for the frontends.
> Ability to unify different backends
Why would that be a GraphQL exclusive thing?
> - The “application data graph” ...
In my generator I supply the models with relationships, type checked using Go. So when creating those models I write code directly, no need to use a pseudo language like GraphQL.
> (not really keen on writing my application logic in SQL)
Maybe you should learn it, as it's really simple and powerful as opposed to the GraphQL language.
But for the record, neither do I write SQL queries using my generator and last time I had to write SQL was in the 2000s when I was still using PHP.
Nowadays I just write my data models and generate the backend and implement the frontend.
And I don't need GraphQL for it.
@ngrx-data for Angular simplifies communication with the backend. And since I generate my notifier/updater too I have real-time updates via websocket.
There's nothing GraphQL offers I don't already do since 2016.
> (not really keen on writing my application logic in SQL) Maybe you should learn it, as it's really simple and powerful as opposed to the GraphQL language. But for the record, neither do I write SQL queries using my generator and last time I had to write SQL was in the 2000s when I was still using PHP. Nowadays I just write my data models and generate the backend and implement the frontend. And I don't need GraphQL for it. @ngrx-data for Angular simplifies communication with the backend. And since I generate my notifier/updater too I have real-time updates via websocket. There's nothing GraphQL offers I don't already do since 2016.