Frontend

Once Bun publishes their Tailwind plugin and adds RSC support, the only reason I think I would even consider Next again would be for the frictionless deployment of toy apps.

The medium-term plan with Bun’s HTTP server Bun.serve()

Make the API complete enough to describe how to build &amp; run your whole app: frontend, backend, routes, api endpoints, services, and all

Jarred Sumner

Once Bun publishes their Tailwind plugin and adds RSC support, the only reason I think I would even consider Next again would be for the frictionless deployment of toy apps.

https://x.com/jarredsumner/status/1883388046814609519

The caching/revalidation functionality of Next is pretty useful for some things IMO. And I personally haven’t found a client side router that’s as intuitive as Next’s

But I definitely find myself reaching for it less and less

likes building things • https://alexgrover.me/links

yeah i agree that is pretty straightforward. just curious, have you run into any issues wrt caching/invalidation? i don’t have much personal experience there, but have heard some horror stories from others

It’s definitely not the best designed feature but they are taking feedback and improving it version by version. The annoying thing is that it caches a lot of stuff by default, but they’re removing that and once you’ve dealt with it a few times it’s not too bad.

It’s possible to build similar functionality pretty easily with Redis or cloudflare for serious projects, but for stuff like a blog or marketing site next works pretty well