REST is fine if you can bare to live inside its constraints. Those constraints aren't necessarily bad and honestly are rather healthy. Its just a way of thinking about the design of your API. Much like OOP is for programming.
The problem comes when we try to do insane things REST was never designed to do or accommodate. GraphQL is great when you grow beyond those constraints. But that shouldn't deter anyone from employing RESTful API design when it fits.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
REST is fine if you can bare to live inside its constraints. Those constraints aren't necessarily bad and honestly are rather healthy. Its just a way of thinking about the design of your API. Much like OOP is for programming.
The problem comes when we try to do insane things REST was never designed to do or accommodate. GraphQL is great when you grow beyond those constraints. But that shouldn't deter anyone from employing RESTful API design when it fits.