> But they should require just a few lines of configuration in GraphQL vs more lines custom boilerplate code in your controller in a traditional MVC framework,

> But they should require just a few lines of configuration in GraphQL vs more lines custom boilerplate code in your controller in a traditional MVC framework, which is a nice win for GraphQL. If it's a few lines of configuration in GraphQL, it's going to be a few lines of configuration or code in the "traditional MVC framework". If it's a lot of code in the "traditional MVC framework", then it's going to be a lot of code in GraphQL as well. The issue with using terms like "traditional MVC framework" is that you will have a hard time making statements that apply to all. > That's a slippery slope leading towards a culture where nothing ever gets done because all the senior engineers default to saying "no" to everything They can just say no to GraphQL then. You shouldn't be mixing culture/politics and technology arguments in one context.