A place for developers to talk about building on Farcaster.

/dev

There’s a lot I agree with and like about this post, but I don’t think client/server unification is something that is going to stick around for the long haul. If your frontend is static, it can and should just be a set of files served by a web server.

There’s a lot I agree with and like about this post, but I don’t think client/server unification is something that is going to stick around for the long haul. If your frontend is static, it can and should just be a set of files served by a web server. https://allenpike.com/2025/javascript-fatigue-ssr

Writer. Building @pinatacloud. Working on simple static site hosting https://orbiter.host \ https://polluterofminds.com

One addendum to this, you don’t need the same app to serve both front end and backend

I’m a monorepo maxi, types and utility packages sharing all the way, then choose the best setup for apps

My usual go to is next.js on the front end and a nice lil koa server on the backend

Designing and building AI systems

https://agents.gladio.ai

Absolutely! I have separated my apps client/server. I don’t prefer monorepos but could easily have them in a monorepo and host them in different places.

How do you manage code reuse and type sharing in this context?

I’ve done a shared “core” package before

That’s a smart idea. I generally don’t manage it. The only re-use for me would be types though. I run a dedicated backend service and a static frontend for almost all my apps so very little opportunity for code re-use