Yes, I've seen the same problems from Gatsby and it wouldnt be my first choice, but I do really like it's use of GraphQL - i think it's a smart way to solve a p

Yes, I've seen the same problems from Gatsby and it wouldnt be my first choice, but I do really like it's use of GraphQL - i think it's a smart way to solve a problem that does exist for some use cases. I like Gatsby's createPage API that lets you programatically create pages from source data at any url, rather than the "traditional" approach of binding views to URL patterns. It's useful for some kinds of static sites that might have a radically different template or data source/model for multiple pages that fit the same URL pattern. Gatsby's use of GraphQL, which can be a pain especially as you scale larger, is nice how it lets you query just the fields you need, so your dehydrated data remains pretty minimal. It's something that I've struggle with when building a site with NextJS - I would have to set up and create my own GraphQL server. Gatsby is a weird one because it has these "advanced" features that really benefit larger sites (or sites with larger ambitions), but Gatsby really can't handle large sites or data.