A place for developers to talk about building on Farcaster.

/dev

Founders

Moore's Law--frightening. Computers get 1000 times as powerful every 15 years.

Luckily for us, our tools get 1000 times slower. No stress, no singularity. Thank you "Next JS"!

I don’t use Next.js unless it makes sense or I absolutely have to. I will admit it’s good when you need full SSR like for e-commerce, but the trade offs are rough imo

DX Engineer | DevRel at OpenZeppelin | Building orbiter.host | stevedylan.dev/links | opinions are my own

Fast, portable, and flexible

Bundles and runs extremely fast 
No vendor lock-in, deploy almost anywhere
Loads of plugins and compatibility across the ecosystem

I will clarify that there is a big difference between Next and Vite though 

Vite is a bundler, similar to webpack. You can use multiple frameworks with it like React, Svelte, etc. It simply helps bundle and run your frontend code, and doesn't necessarily mean it will be SSR. That depends how you deploy it. 

Next.js is an opinionated SSR framework that uses react with a bunch of other proprietary Vercel tools. It's specially designed to be run on Vercel, which means while you can try to self host it or deploy it elsewhere, you will have issues due to the tightness of that integration. It's why 3 different teams are building a more open and compatible version of Next that still isn't quite there

Se siente mejor y no. Puedo amar más y más que antes. Lo que ella ha dicho siempre importa. 

Cambia de cuerpo, altera la mente, pero me arrodillo igual. ¡De ro

Fast, portable, and flexible

Bundles and runs extremely fast 
No vendor lock-in, deploy almost anywhere
Loads of plugins and compatibility across the ecosystem

I will clarify that there is a big difference between Next and Vite though 

Vite is a bundler, similar to webpack. You can use multiple frameworks with it like React, Svelte, etc. It simply helps bundle and run your frontend code, and doesn't necessarily mean it will be SSR. That depends how you deploy it. 

Next.js is an opinionated SSR framework that uses react with a bunch of other proprietary Vercel tools. It's specially designed to be run on Vercel, which means while you can try to self host it or deploy it elsewhere, you will have issues due to the tightness of that integration. It's why 3 different teams are building a more open and compatible version of Next that still isn't quite there https://opennext.js.org

I’m still building with Nextjs because a] Lee Robinson is a kind and generous DevRel leader, b] their documentation is high value and updated. But, a few apps on the idea bench could use a new frameWORK. Pitch me the value of Vite < 160 characters.

Very true; Vite is so damn good 😭

I think back in the day handling a server/backend was much harder than it is now. For most things you can use a Cloudflare worker and those can be deployed in a single CLI command. Use a framework like Hono and you get a fantastic developer experience when building your API. 

If you’re interested, this is one of the things I’m trying to tackle in bhvr.dev: a simple framework for fullstack apps. It’s not a drop in replacement for everything, but imo it provides a simple alternative to Next if you just want client and server in the same repo. I’m also working on a pretty slick integration with https://orbiter.host which will make that transition even more seamless!

noob programmer | badminton athlete turned hobbyist | metroidvania enthusiast | casting @ /vaxitas

Oooh okay, checking these out, thanks for sharing! I came across Orbiter yesterday I think. I'm actually looking for a simple solution to host my personal site. I was considering GitHub pages, but this seems really enticing. I'll keep you posted and reach out if I need any help 🙌

I honestly think Vite's more than enough for SSR/SSG needs. It doesn't enforce filesystem based routing and you can fetch whatever data you need to render such pages in a single script and also hydrate.

Personally, the main advantage to using Next for me (and most others who come from a frontend background) has been the ease of deployment.

I don't think that's a strong enough incentive to keep up with an ever changing ecosystem. Might as well learn CI/CD stuff instead.

I personally have been dropping nextjs for so long, unless job requires me to do it. my go to always has been react-vite. its also for the sake of DX and reducing the abstraction. when I need a backend, I spin up a hono API.

well previously I was using remixjs, but remix's decision to move into react-router framework is the most confusing decision I've ever used. so here I am with the most simple stack.