Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
1–10 of 28 posts
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#2[deleted]
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#3I wonder if this blog post was prompted by this: https://news.ycombinator.com/item?id=43481295
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#4"Fortunately, thanks to Vercel’s outreach, we’ve established lines of communication with the Next.js team. With this in place we hope to gain better insights into upcoming changes to the framework."
So instead of having it in open, Netlify now have their own channel of communication with Vercel. This still continue to feel like a closed garden and makes it difficult for small vendors to have proper NextJS hosting.
(Disclosure: I am running DollarDeploy which allows hosting NextJS (amongst others) on your own server. And we don't use docker!)
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#5"Fortunately, thanks to Vercel’s outreach, we’ve established lines of communication with the Next.js team. With this in place we hope to gain better insights into upcoming changes to the framework." So instead of having it in open, Netlify now have their own channel of communication with Vercel. This still continue to feel like a closed garden and makes it difficult for small vendors to have proper NextJS hosting. (D…
Unfortunately commercial companies tend to work behind closed doors/gardens. We are working on Low-Ops.com and would love to fully support NextJS. Self-hosting is the future :)
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#6"Fortunately, thanks to Vercel’s outreach, we’ve established lines of communication with the Next.js team. With this in place we hope to gain better insights into upcoming changes to the framework." So instead of having it in open, Netlify now have their own channel of communication with Vercel. This still continue to feel like a closed garden and makes it difficult for small vendors to have proper NextJS hosting. (D…
(disclaimer: I work at Netlify)
It's not a 1:1 channel, we're pushing for as much work in the open as possible, and extending the OpenNext group to more members.
IMHO one major challenge is the amount of work one has to do to build an adapter, if we can make the spec leaner and move logic out of e.g. the CacheHandler, that's gonna make it easier for you to create your own (or you could state that some features/modes are not supported - but for that, you'd need to have a very good idea of what these even are)
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#7I wonder if this blog post was prompted by this: https://news.ycombinator.com/item?id=43481295
100%. The OP said he works for Netlify and this seems like a verbatim repost of theirs.
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#8Hey bro would you like a SaaS Convenience layer for your SaaS convenience layer? No, no the issues and costs won't compound.
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#9[deleted]
Re: Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
#10"Fortunately, thanks to Vercel’s outreach, we’ve established lines of communication with the Next.js team. With this in place we hope to gain better insights into upcoming changes to the framework." So instead of having it in open, Netlify now have their own channel of communication with Vercel. This still continue to feel like a closed garden and makes it difficult for small vendors to have proper NextJS hosting. (D…
(disclaimer: I work at Netlify) It's not a 1:1 channel, we're pushing for as much work in the open as possible, and extending the OpenNext group to more members. IMHO one major challenge is the amount of work one has to do to build an adapter, if we can make the spec leaner and move logic out of e.g. the CacheHandler, that's gonna make it easier for you to create your own (or you could state that some features/modes…
Thank you for clarifying! There is a open source cache adapter but it does not support NextJS 15 at the moment.