Congrats on the launch! While the focus is on humans, I found many of the principles here to be very relevant for building with AI.
With LLMs able to generate the "magic" with ease, I can see the role of frameworks shifting a bit. Instead of hiding complexity, it's surely more beneficial to expose the primitives clearly enough that both you and an LLM can follow the request lifecycle.
The bet on Cloudflare is pretty bold, but it does make sense given how unique their products like DO and Workers are. I suppose there's not much of an escape hatch if you ever needed one?
> With LLMs able to generate the "magic" with ease, I can see the role of frameworks shifting a bit. Instead of hiding complexity, it's surely more beneficial to expose the primitives clearly enough that both you and an LLM can follow the request lifecycle.
100%.
I kinda feel like we've fooled ourselves into creating these domain specific languages for frameworks, where we glue things together using magic, and just dealing with the features of the language, the browser and the network make a lot of sense in the AI world. And our framework is actually much less complicated than I think a lot of them are...
> I suppose there's not much of an escape hatch if you ever needed one?
I of course don't want to be vendor locked in, so I've started working on something called open durable objects, and I have a concept for something called open bindings.
these are the two core technical solutions that the framework really needs from Cloudflare. This does not include durability in the same way you get it from Cloudflare: it will run on a single machine.
But jokes aside, I use Beanstalk quite a bit and it's mighty leaky, don't find it all that comparable to stuff like fly.io, although in spirit it's the same thing I suppose.
Before these changes go live (and before the grace period begins) you'll be able to see your current pricing vs. new pricing in the dashboard, so you can optimize from there.
Also a fan of Vercel and I'm very appreciative of the work they contribute to the React/JS ecosystem. Errors in human judgement happen and while they may have taken the appropriate action against the employee, I don't feel like they've reassured me enough that there are processes in place to prevent this happening in the future.
How do you handle global infrastructure on AWS/GCP?
The performance is great in the US for my Next.js app on GCP/AWS as that's where I deploy to, but elsewhere the TTFB is poor. Deploying to multiple regions would probably end up costing more than Vercel for us.
With LLMs able to generate the "magic" with ease, I can see the role of frameworks shifting a bit. Instead of hiding complexity, it's surely more beneficial to expose the primitives clearly enough that both you and an LLM can follow the request lifecycle.
The bet on Cloudflare is pretty bold, but it does make sense given how unique their products like DO and Workers are. I suppose there's not much of an escape hatch if you ever needed one?