Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Netlify acquires Gatsby

netlify.com

Post reply on HN
Print view View original

131–140 of 147 posts

Re: Netlify acquires Gatsby

#131

Post by sebmellen »

CharlesW wrote: post #96
maccard wrote: post #92

Earlier quoted context omitted.

> $2,500/mo to host a static site is ludicrous. But it's not to host a static site, it's one click CD, multiple environments, global CDN, and a few more things. I'm not going to say how mu h it is worth, but if you just want a static site with a domain you can do it for free/sub $10 on many many providers.

> But it's not to host a static site, it's one click CD, multiple environments, global CDN, and a few more things. What can you do for $2,500 on Netlify you can't do on Vercel for $20/user/month?

SSO is probably the only thing. Other than that, no idea. Netlify pulled the same stunt with us and we left. They must have burned many bridges by now.

Re: Netlify acquires Gatsby

#132

Post by Rauchg »

parttime-hire wrote: post #126
Rauchg wrote: post #117

Earlier quoted context omitted.

> They advertised open standards and then did a bait-and-switch to proprietary systems 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-compli…

Nextjs edge middlewares broke compatibility with workers by adopting async local storage API.

You'll also be happy to hear this :) https://twitter.com/robpalmer2/status/1620869647322189824

> ECMAScript excitement

> Congrats to Justin Ridgewell @vercel & @legendecas on advancing the "Async Context" proposal to Stage 1 at @TC39 today

Re: Netlify acquires Gatsby

#133

Post by subpixel »

joshmanders wrote: post #45

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 think you’re missing the forest for the trees. Gatsbyjs is as good as dead, but this Valhalla thing has legs, and the Gatsby team (as much of it as they have hired) has deep experience tackling problems around ingesting data from a wide array of sources for efficient web delivery.

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

Re: Netlify acquires Gatsby

#134

Post by satvikpendem »

bombcar wrote: post #116
ilrwbwrkhv wrote: post #91

Earlier quoted context omitted.

Just get a $5 digital ocean droplet and throw nginx on it. All the static hosting in the world at your fingertips.

Caddy is even simpler.

Coolify is even simpler IMO after using Caddy.

https://coolify.io

Re: Netlify acquires Gatsby

#135

Post by merlinoa »

I host an old blog on netlify. I don't update it anymore, but a few months ago I started seeing a large uptick in subscribers. They were all subscribing through the netlify subscription form. It was around 8 to 10 new subscribers a day where before it was one every couple months. I emailed several of the new subscribers and got no response. After a few days I strongly suspected these were not real subscribers.

But why would someone waste their time adding a few subscribers to my old, non updated blog everyday? A couple weeks later I got an email from Netlify saying that I was being upgraded to a payment plan because of the amount of activity on my Netlify hosted form.

Re: Netlify acquires Gatsby

#136

Post by hoofhearted »

joshmanders wrote: post #45

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.

Future prediction: Vercel acquires Netlify.. Especially for the Netlify admin feature where a user can create pages in a WYSIWYG editor and save them in Git. Pretty much would make Wordpress obsolete at that point in my opinion.

Don’t hold me to it, just an educated guess.

Re: Netlify acquires Gatsby

#137

Post by lancefisher »

bradgessler wrote: post #70
corywatilo wrote: post #69

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?

I’ve been happy with Google’s Firebase Hosting. It’s confusing branding, but almost a drop in replacement. https://firebase.google.com/docs/hosting

Re: Netlify acquires Gatsby

#138

Post by phawksworth »

kilburn wrote: post #113
phawksworth wrote: post #84

Earlier quoted context omitted.

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

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

I don't quite agree. Gatsby Inc have been doing a ton of work in this area, and it is really impressive. It's one of the reasons that its platform has been such a draw to larger companies with more complex data and content sourcing needs.

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

Re: Netlify acquires Gatsby

#139

Post by Alifatisk »

reducesuffering wrote: post #41
onion2k wrote: post #5

Earlier quoted context omitted.

I think it's an acquihire. They don't necessarily want Gatsby. They want the team who built Gatsby.

I'm surprised this was the only other comment so far about it. It has to be an acquihire. Gatsby is a dead framework going forward.

Why do you call it a dead framework?

Re: Netlify acquires Gatsby

#140

Post by Alifatisk »

joshmanders wrote: post #45

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 bad news for full stack JavaScript applications and ecosystem. > Open source is losing and something needs to change.

You still have Nuxt ;)

Post reply on HN