Lack of strong points, all the arguments here indicate you simply don’t know how to implement a proper GraphQL backend, with all the resources online, and I doubt things will get better for you for REST API… the reality is cruel but true…
There's definitely more resources + best practices for REST API than GraphQL. I'm arguing that at the beginning of the project, it's not worth investing in the additional tooling and introducing the additional friction when onboarding engineers who have not worked with GraphQL.
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.
Lack of strong points, all the arguments here indicate you simply don’t know how to implement a proper GraphQL backend, with all the resources online, and I doubt things will get better for you for REST API… the reality is cruel but true…
There's definitely more resources + best practices for REST API than GraphQL. I'm arguing that at the beginning of the project, it's not worth investing in the additional tooling and introducing the additional friction when onboarding engineers who have not worked with GraphQL.