Anyway, I'm sure this will be said elsewhere in the thread but it bears repeating — the Next team similarly works hard to make sure that your Next apps can be self-hosted and run on other platforms.
While Vercel's intentions are good, and your personal intentions are beyond reproach, this strategy all but ensures eventual vendor lock-in without explicitly saying so. Vercel's compatibility will increase over time and other vendors will have best-effort implementations of certain features, but never the complete feature matrix. The industry (esp. medium/large companies) will quickly pick on the relation of "Vercel is needed for ease of mind when using SvelteKit in production", as I've heard from many companies considering/using Next.js. Do people use Next.js without Vercel? Yes. Do companies evaluating Next.js consider it vendor-locked? If they're experienced, yes.
Gatsby's Vahalla Content Hub supports multiple (not all at once) meta frameworks like Next.js, Gatsby, Nuxt, Remix, SvelteKit, etc...
https://www.gatsbyjs.com/products/valhalla-content-hub/
Edit: typo
tl;dr all features work self-hosted
Also, I think Netlify and company know that a framework that is locked in won't be adopted. The history of mainstream developer tooling over the last thirty years is a migration away from proprietary languages and frameworks, and it's going to take more than a few rogue JS fullstack frameworks to change that.
I recognize that fear. And have made similar observations of the current landscape.
Our hope in this instance is actually that the opposite is true.
The goal of this acquisition is not to OWN a JavaScript framework. Gatsby Inc is far bigger than Gatsby.js
The Gatsby.js project will join the Solid.js and Eleventy open source projects that Netlify already support through full time employment but who'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'd like to try to provide the best experience and support for whatever those might be down the line. We can't own it all. We'd prefer to support it.
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.
This sounds ridiculous to me. The "powerful build and content orchestration tooling" of Gatsby Inc. is basically the same stuff that everyone else is doing in this space. This includes:
- The traditional Gatsby competitors (Vercel, GH Pages).
- Heroku, Fly.io and similar.
- Cloud-specific options such as AWS Amplify.
Theo had a pretty perceptive take on this on his stream yesterday. Worth a look. https://www.youtube.com/watch?v=bJc9UYva46I&t=5384s
Meanwhile, with so many people talking about the acquisition as if Netlify purely acquired the Gatsby.js framework, I find it helpful to frame it like this:
Gatsby Inc is to Gatsby.js as Vercel is to Next.js
Netlify acquired Gatsby Inc
However, there is still a line that, when crossed, turns you into a regular old spammer. You are walking _very_ close to that line.
The Valhalla platform was "launched" 2 months ago. Even today there's ZERO public technical documentation on it. You can only find a bunch of marketing slides, SEO-ridden blog posts etc. saying that it's great, plus a video showing a few queries against a regular GraphQL server.
Please stop pretending that this quasi-vaporware platform is the best thing since french fries. Thanks.
God forbid there's actual paid engineers and support behind popular JavaScript tooling.
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'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'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't attempt to control SolidJS or 11ty now.
Every single fortune 1000 company has the problem Valhalla is trying to solve. Most have painted themselves into a multi-CMS corner and are closer to copy/paste solutions for getting content where it’s needed than the sort of GraphQL approach Gatsby (the company) is advocating.
The marketing-speak here is something like “all your content, no matter where it lives, delivered to your customers, no matter where they are.”
Don’t hold me to it, just an educated guess.
This is bad news for full stack JavaScript applications and ecosystem. This is gonna cause vendor lock-in, it's already showing in some of them. Open source is losing and something needs to change.
I am seeing a future where you have to rewrite your whole app in a different framework just to change hosts.