Backend

Javascript still needs its Rails/Django equivalent. Next.js has empowered a bunch of frontend devs to build fullstack applications, but there’s a ton of footguns and the flexibility still has people floundering in problems long-solved by other frameworks.

Head of Product Engineering @polymarket prev: @rainbow, Truework ● 1/3 of rectanglefactory.com ● nickbytes.com

I recently built an app and used NextJS to produce client-only code which I bundled into a Go binary. Go was my web server and API backend.

The open web is dead, long live the open web. ⌐◨-◨

Building /warpcast and /farcaster

— gabrielayuso.com

That's kinda wild way to use Next, but whatever works works!

I just used Next as an easy way to bootstrap a React project so didn't take full advantage of the other Next JS features.

It did give me the flexibility to split into a web server and an API server if I wanted to (I did it for debugging a few times). Using NextJS to serve the UI and Go to serve the API.

Yea, kinda nice that you can implement the "backend for frontend" architecture if you want. I think that pattern is super helpful for big orgs w/ lots of microservices or legacy APIs.

yeah - the Go API was essentially an abstraction layer on top of many different services (both 1P and 3P) running on different environments.