Live data from Hacker News

Netlify acquires Gatsby

netlify.com

141–147 of 147 posts

Re: Netlify acquires Gatsby

#141

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

Every time i read these comments I am glad that Evan (creator of Vue and Vite) decided to be independent of Tech Companies

Re: Netlify acquires Gatsby

#142
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?

That's not a fair comparison. Looki at Netlify[0] and Vercel's [1] pricing sites, the per-user pricing for the "pro" tiers is the same and Vercel gates the features that are in the Netlify "business" tier behind an enterprise contact-us paywall.

I suspect that if you're using these "as expected", your bill on both sites would be the same.

[0] https://www.netlify.com/pricing/ [1] https://vercel.com/pricing

Re: Netlify acquires Gatsby

#144

Earlier quoted context omitted.

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

I understand that you're a DX at Netlify and your job is to advocate for whatever tech happens to be on your backyard. You openly acknowledged it and I thank you for it.

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.

Re: Netlify acquires Gatsby

#145
post #129

Earlier quoted context omitted.

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

The way to think about our edge runtime is (which is something you're seeing across the board in the industry) is that there's a pure subset of WinterCG APIs, plus Next.js enabling a compatibility layer on top to play nicely with the _vast_ npm ecosystem. Everything about the feature you're referring to is open source. We're expanding our documentation to better present this compatibility layer.

There's no compatibility layer for AsyncLocalStorage though, and it's not something that can be polyfilled without runtime support. Requiring it in Next.js has forced all the other edge runtimes to implement it in its un-standardised form if they want to support Next.js. Putting it on globalThis is particularly egregious in a runtime that's meant to be standards-compliant and championing the AsyncContext standard. And what about Headers.prototype.getAll()? That's a non-standard method on a standard object that is only implemented by Cloudflare, yet Next.js started using it in a patch release. I get it: you have no incentive to make life easier for other runtimes as used by competitors and AsyncLocalStorage is a really useful API, but people should be under no illusion that you're being a good citizen with the standards here.

Re: Netlify acquires Gatsby

#146

Earlier quoted context omitted.

Caddy is even simpler.

Coolify is even simpler IMO after using Caddy. https://coolify.io

If by simpler you mean there is literally zero content on the page:

    $ http https://coolify.io/
    HTTP/1.1 200 OK
    CDN-Cache: HIT
    CDN-PullZone: 355073
    CDN-RequestCountryCode: US
    CDN-RequestId: 196ca62f96058...
    CDN-Status: 200
    CDN-Uid: bb1c6a05-...
    Connection: keep-alive
    Content-Length: 0
    Date: Fri, 03 Feb 2023 20:46:54 GMT
    Server: BunnyCDN-ASB1-925

Re: Netlify acquires Gatsby

#147

Earlier quoted context omitted.

Coolify is even simpler IMO after using Caddy. https://coolify.io

If by simpler you mean there is literally zero content on the page: $ http https://coolify.io/ HTTP/1.1 200 OK CDN-Cache: HIT CDN-PullZone: 355073 CDN-RequestCountryCode: US CDN-RequestId: 196ca62f96058... CDN-Status: 200 CDN-Uid: bb1c6a05-... Connection: keep-alive Content-Length: 0 Date: Fri, 03 Feb 2023 20:46:54 GMT Server: BunnyCDN-ASB1-925

I see the page, not sure if you have something blocking your connection, or the CDN near you is faulty.
Post reply on HN