> we are thrilled to join forces
How many people were let go as a result of this acquisition? (I know for a fact that the number is not zero)
Netlify acquires Gatsby
121–130 of 147 posts
Re: Netlify acquires Gatsby
#122Netlify 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?
surge.sh is very very back to basics, and is amazing for small-ish static sites
Re: Netlify acquires Gatsby
#123Earlier quoted context omitted.
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…
> 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…
Thank you Guillermo. One thing I am still curious about is, is there still a difference between serverside rendering and static site generation for things such as next/image, next/font, etc? Last time I tried SSG, next/image was not supported, but I could use a third party tool to optimize my images correctly, so I didn't understand why next/image couldn't do the same optimization at build time without relying on a CDN as in the case of SSR.
Re: Netlify acquires Gatsby
#124Earlier quoted context omitted.
What are the alternatives?
Next.js the comparison shown in those charts
I would not consider Next.js an alternative as it's missing a lot of the static website generation features.
I don't think that it has server side GraphQL and Typescript support with data preloading from headless CMSs.
Re: Netlify acquires Gatsby
#125Earlier 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…
Thank you Guillermo. One thing I am still curious about is, is there still a difference between serverside rendering and static site generation for things such as next/image, next/font, etc? Last time I tried SSG, next/image was not supported, but I could use a third party tool to optimize my images correctly, so I didn't understand why next/image couldn't do the same optimization at build time without relying on a C…
One fascinating thing (especially in view of this topic) about `next/image` is that the primary reason we decided not to optimize upon `next build` or `next export` is that we'd have all these customers migrating from Gatsby telling us their build performance was holding them back, and a big chunk of that was `sharp` optimization and overly eager static generation. Image optimization fits a "dynamic" model much better.
In fact, look at this example I tweeted today: https://twitter.com/rauchg/status/1620821476499947523
… it shows how Vercel lazily optimizes _specifically_ (1) for the images in viewport and (2) for the devices requesting those images. And new pages and images can be added without redeploying.
I think we could still put image optimization behind a flag with a durable cache at build time (think: `next export --optimize-images`), but it's always been hard to prioritize it as the world moves further away from pure-static solutions
As a userspace alternative, I don't think it'd be too hard to do a post-build script that runs `sharp` on a `source-images` folder, outputs it to `public/static-images` with content-addressable checksums, and sets `cache-control` in `next.config.js` `headers` to `public, max-age=31536000, immutable`. Oh, and you could first check if there work has already been done in `.next/images-cache` or something that the CI provider would cache across builds, to make it a bit faster.
Re: Netlify acquires Gatsby
#126Earlier quoted context omitted.
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…
> 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.
Re: Netlify acquires Gatsby
#127Re: Netlify acquires Gatsby
#128Earlier 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.
And all of the infrastructure management for free!!!!
There is hardly any, if you are hosting static dirs. It's literally one file, the nginx.conf.
Re: Netlify acquires Gatsby
#129Earlier 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.
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.