Comment by azangru
2 days ago
It still baffles me why Netlify did that. Gatsby seemed to have already been dying, even before the acquisition; and it didn't look like Netlify was planning to invest in it.
2 days ago
It still baffles me why Netlify did that. Gatsby seemed to have already been dying, even before the acquisition; and it didn't look like Netlify was planning to invest in it.
Netlify didn't buy Gatsby for the framework. They wanted the hosting business and the GraphQL thing. They said this at the time, and it's true. It was barely resourced. Cloudflare is only interested in the framework (because Astro has nothing else).
Source/disclosure: I worked at Gatsby, Netlify, Astro and Cloudflare
Why did they want Gatsby's graphQL thing? What was attractive about it?
Seemed a good idea at the time. The unified data layer was always the best thing about Gatsby (which is why I nicked the idea for the Astro content layer), but maybe not as a hosted product