This quote about #graphql very much applies to a lot of the "modern" #javascript ecosystem. It's a good illustration of how concerns change when you become responsible for your code. Mind boggling!
"as the years have gone on and I have had the opportunity to deploy to environments where non functional requirements like security, performance, and maintainability were more of a concern"
Follow
@brianleroux I continue to feel that GraphQL (or rather, something like it) would have been a much better fit as a server-side data layer abstraction, that itself never goes over the network (and is just a library function call); because collating different data sources is the part that the model actually good at!
