[huksley]

"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!)

[erozzy]

(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)

[huksley]

Thank you for clarifying! There is a open source cache adapter but it does not support NextJS 15 at the moment.

[serhalp]

Ooh, interesting. We didn't know about this. Is this it? https://github.com/caching-tools/next-shared-cache/tree/cana...

[huksley]

yes, there is even the official example here https://github.com/vercel/next.js/tree/canary/examples/cache...

but it does not work because of NextJS 15.

I changed the example to point to latest NextJs 14 and fixed some cache-handler bugs it works fine, and I deploy it successfully with DollarDeploy to DO VPS https://github.com/huksley/next-cache-handler

[serhalp]

This is a great point and definitely something we're mindful of. That sentence actually ended with "and share these with the community" in the draft, but we can't make promises on behalf of the Next.js team.

Our hope is that the OpenNext initiative's growth and connections with the Next.js team is just a first step toward shifting some Next.js governance out to the open. The article calls out that the OpenNext members are hoping to contribute to public RFCs in the future, with Next.js core team collaboration.

[xiwenc]

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 :)