Earlier quoted context omitted.
Sounds like they behaved exactly how you expected them to. You can't get upset because the threshold was passed.
IIRC they had recently added a user cap on self-serve customers which was new and led to this. The new pricing deck they sent was "It will be $3,500/mo, but until the end of the month, you can get it for only $2,500!" (Pricing approx.) $2,500/mo to host a static site is ludicrous.
Netlify acquires Gatsby
111–120 of 147 posts
Re: Netlify acquires Gatsby
#112People still use Gatsby?
Re: Netlify acquires Gatsby
#113Vercel has Next.js, Shopify just acquired Remix, now Netlify Gatsby. 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.
[Disclaimer: I work in the Netlify DX team] 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…
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.
Re: Netlify acquires Gatsby
#114Re: Netlify acquires Gatsby
#115Netlify lost my trust a year ago when they tried to increase our company's pricing more than 10x. (We were paying ~$200/mo, then they tried to force us into a $2,500+ plan because we were 1 seat over their self-serve threshold.) From my perspective, they were adding features just to find ways to grow revenue. (I get it, you don't have a huge moat by simply hosting static sites.) But their features seemed very out of…
If you want “old reliable” that works how you expect it to, with the ease of use of a modern platform, and one that won’t break the bank, my pick would be Cloudflare or Render.
Re: Netlify acquires Gatsby
#116Earlier quoted context omitted.
Is there a “back to the basics” company or offering for hosting static sites that is essentially what Netlify was when it launched?
Just get a $5 digital ocean droplet and throw nginx on it. All the static hosting in the world at your fingertips.
Re: Netlify acquires Gatsby
#117Netlify lost my trust a year ago when they tried to increase our company's pricing more than 10x. (We were paying ~$200/mo, then they tried to force us into a $2,500+ plan because we were 1 seat over their self-serve threshold.) From my perspective, they were adding features just to find ways to grow revenue. (I get it, you don't have a huge moat by simply hosting static sites.) But their features seemed very out of…
Vercel has betrayed my trust and expectations perhaps more than any other provider. They advertised open standards and then did a bait-and-switch to proprietary systems. They also broke our automated deployment pipeline out of the blue and called it a feature, not a bug. They don’t seem to care much about security, either. [1] If you want “old reliable” that works how you expect it to, with the ease of use of a moder…
I'd love more detail on this. We have made major investments in open source and ensuring Vercel is an open platform.
◆ The Vercel Build Output API exposes all the underlying primitives of the platform for every framework to take advantage of (https://vercel.com/blog/build-output-api)
◆ We've diligently invested in standard-compliant API signatures. Serverless Functions adopted the Node.js request / response standard (as opposed to e.g.: AWS Lambda inventing a new one) and Edge Functions adopt the Web standard. We've joined WinterCG to foster this standardization effort (https://wintercg.org/)
◆ We've always invested in API compatibility between local development, self hosting and Vercel infrastructure (e.g.: `vc dev` is open source https://github.com/vercel/vercel).
◆ We're continuing to invest here. Next.js and Vercel build outputs are always getting more detailed, we're exploring support for running build outputs locally (`vc start`) as an open source offering, etc.
> they don’t seem to care much about security
We added support for your feature request, and security remains the top priority of the company. Some recent ships:
◆ https://vercel.com/changelog/access-tokens-can-now-be-scoped...
◆ https://vercel.com/changelog/share-environment-variables-acr...
◆ https://vercel.com/changelog/expiration-dates-now-available-...
◆ https://vercel.com/changelog/protected-preview-deployments-a...
◆ https://vercel.com/changelog/increased-security-with-view-on...
◆ https://vercel.com/changelog/enhanced-security-with-new-api-...
Re: Netlify acquires Gatsby
#118Vercel has Next.js, Shopify just acquired Remix, now Netlify Gatsby. 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.
Re: Netlify acquires Gatsby
#119Vercel has Next.js, Shopify just acquired Remix, now Netlify Gatsby. 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.
Counter to this, there’s SvelteKit, for example, which provides „adapters“ for the different platforms, eg. Netlify, Vercel and Cloudflare. I hope that’s the way we’re going to oppose this movement as a whole.
Re: Netlify acquires Gatsby
#120This kind of stuff is annoying. Netlify had no need to acquire this. They just want to increase their revenue. As a Hugo user on Netlify, I hope this doesn't affect me negatively.