<story><title>Netlify acquires Gatsby</title><url>https://www.netlify.com/press/netlify-acquires-gatsby-inc-to-accelerate-adoption-of-composable-web-architectures/</url></story><parent_chain><item><author>joshmanders</author><text>Vercel has Next.js, Shopify just acquired Remix, now Netlify Gatsby.&lt;p&gt;This is bad news for full stack JavaScript applications and ecosystem. This is gonna cause vendor lock-in, it&amp;#x27;s already showing in some of them. Open source is losing and something needs to change.&lt;p&gt;I am seeing a future where you have to rewrite your whole app in a different framework just to change hosts.</text></item></parent_chain><comment><author>phawksworth</author><text>[Disclaimer: I work in the Netlify DX team]&lt;p&gt;I recognize that fear. And have made similar observations of the current landscape.&lt;p&gt;Our hope in this instance is actually that the opposite is true.&lt;p&gt;The goal of this acquisition is not to OWN a JavaScript framework. Gatsby Inc is far bigger than Gatsby.js&lt;p&gt;The Gatsby.js project will join the Solid.js and Eleventy open source projects that Netlify already support through full time employment but who&amp;#x27;s roadmaps and operations are their own. Using those tools is not a means for Netlify to funnel developers into our platform, nor a means to attempt to lock users in. Our philosophy is that an abundance and variety of such tools is good for the web (and as a result good for us). Also that more tools will come in future and that we&amp;#x27;d like to try to provide the best experience and support for whatever those might be down the line. We can&amp;#x27;t own it all. We&amp;#x27;d prefer to support it.&lt;p&gt;Meanwhile, Gatsby Inc have created very powerful build and content orchestration tooling which is currently only available to Gatsby.js users. This acquisition will result in those capabilities being made available to any frameworks further helping all comers to the frameworks landscape.</text></comment>
<story><title>Netlify acquires Gatsby</title><url>https://www.netlify.com/press/netlify-acquires-gatsby-inc-to-accelerate-adoption-of-composable-web-architectures/</url></story><parent_chain><item><author>joshmanders</author><text>Vercel has Next.js, Shopify just acquired Remix, now Netlify Gatsby.&lt;p&gt;This is bad news for full stack JavaScript applications and ecosystem. This is gonna cause vendor lock-in, it&amp;#x27;s already showing in some of them. Open source is losing and something needs to change.&lt;p&gt;I am seeing a future where you have to rewrite your whole app in a different framework just to change hosts.</text></item></parent_chain><comment><author>ascorbic</author><text>I work at Netlify on framework integrations.&lt;p&gt;We plan to do the exact opposite. Right now there are features in Gatsby that were built to support only Gatsby Cloud. I know this all too well as I had to reverse engineer them to implement them on Netlify! We don&amp;#x27;t want that anymore. I am hoping that Gatsby will be like SvelteKit, Remix, Astro, Nuxt etc and will be platform agnostic again. Whether that&amp;#x27;s via an adapter pattern (my preference) or something else remains to be seen. This acquisition was not about controlling a framework, just as we don&amp;#x27;t attempt to control SolidJS or 11ty now.</text></comment>