4 ms·
Yeah I got that you think they're "overly complex" but they literally have nothing to do with each other. REST is simple compared to GraphQL if you have no sta
by slver 5y ago
Yeah I got that you think they're "overly complex" but they literally have nothing to do with each other.
REST is simple compared to GraphQL if you have no standards at all and just slap everything with ad-hoc CRUD resources at will. That's what you do, don't you?
Ever tried to implement OData or OpenApi or any kind of structured API covering HATEOAS at all? Do you actually define your own content types, with MIME and so on? My guess is no. You're not doing REST. You're doing JSON CRUD RPC.
REST is a quagmire of competing half-completed standards trying to do what GraphQL does in one step and with least amount of "maybe this maybe that" situations.
- jlouis 5y agoGraphQL is like 3k to 4k Lines in the server side. Not exactly a large system.