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

software artist | building /outpaint | ex: @coinbase ex: bisontrails | seeker of the flow state | artivilla.com

I've been using Elysia

https://elysiajs.com/

I haven't built any sufficiently complex front-end apps recently, so my usage with Elysia has either by 1) as an API server, 2) SSR (no client-side routing), or 3) API server + a catch-all route to serve an SPA that uses its own routing. But agreed for 3, the DX feels a little funky

I use hono for my server but that doesn’t replace my client side routes. no sure if they compare?

and thus API is so much more uglier than pages/