Live data from Hacker News

Netlify acquires Gatsby

netlify.com

81–90 of 147 posts

Re: Netlify acquires Gatsby

#81

Netlify 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…

> From my perspective, they were adding features just to find ways to grow revenue. Why else would they add features?

Try to solve user problems? (Maybe they were, just not ours.)

Re: Netlify acquires Gatsby

#82

Netlify 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…

Sounds like they behaved exactly how you expected them to. You can't get upset because the threshold was passed.

[deleted]

Re: Netlify acquires Gatsby

#83
post #66
post #59

Earlier quoted context omitted.

How exactly does Netlify shut down competition with this?

As some people mentioned elsewhere, the acquisition is probably more focused on Gatsby Cloud than Gatsby itself (which remains open source), and Gatsby Cloud is a Netlify competitor.

> Gatsby Cloud is a Netlify competitor

That's a bold assumption. What's Gatsby Cloud's market share? Zero-point-something percent?

Re: Netlify acquires Gatsby

#84

Vercel 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 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.

Re: Netlify acquires Gatsby

#85

Netlify 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…

Is there a “back to the basics” company or offering for hosting static sites that is essentially what Netlify was when it launched?

We use and swear by Opalstack.com, which is made by some of the same peeps that worked for the may-as-well-be-defunct Webfaction.

Full SSH access, generous limits, very active community.

Re: Netlify acquires Gatsby

#86

Vercel 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.

> This is gonna cause vendor lock-in

God forbid there's actual paid engineers and support behind popular JavaScript tooling.

Re: Netlify acquires Gatsby

#87
Was scanning the page really quickly and though that Netflix had acquired the Gatsby franchise and we could look forward to "Great Gatsby 2 - The Vendetta", "The Greatest Gatsby", "Gatsby Strikes Back" and so on.

Re: Netlify acquires Gatsby

#88

Vercel 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.

I work at Netlify on framework integrations.

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.

Re: Netlify acquires Gatsby

#90

Vercel 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.

These frameworks spit out a bunch of static files to serve, which you can host just about anywhere. They also all use React, which means if you did want to switch frameworks, the majority of your code should be usable either as-is or with a little elbow grease. The situation you describe is just not something I'm worried about
Post reply on HN