The really dumb part is that GraphQL has more restrictions than JSON on property names, so you can't actually render arbitrary JSON data with gatsby without bre

The really dumb part is that GraphQL has more restrictions than JSON on property names, so you can't actually render arbitrary JSON data with gatsby without breaking the GraphQL schema and getting a ton of errors. It seemed nice at first, but the way they tell you to deal with images and other resources is ridiculous overengineered and gets in the way. If you throw real data at it, your builds explode from seconds to minutes. Ill considered, chasing too many fads, and the inability to turn it all off if you don't need it. That's what gatsby felt like.