Frontend

this is a very @samuellhuber.eth-coded blog post

summary_large_image

We moved off Next.js 👀

https://t.co/ZRBeq2lqkl

Let us know what you think 🌶️🤔

Documenso

this is a very @samuellhuber.eth-coded blog post

https://documenso.com/blog/why-we-moved-off-next-js

https://x.com/documenso/status/1907019629652058196?s=46&t=8l54n7dYtHePgMrhGh-cUw

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

engineer @base | /farhack /tap /cortex | dylansteck.com

oops the tag didn’t go through! 

cc @samuellhuber.eth I think you’re gonna like this one :)

agreed on all of these points as they’re pains I’ve experienced directly

I think it’s really easy to follow the latest conventions but it feels like when you use some of them in NextJS not only is the architecture changing quite a bit but it’s boxing you in/leaving you with performance tradeoffs at times

all that being said there’s a lot about next I still really like and I use it a ton

My problem isn’t NextJS it’s what I see people do with it as it has next to no guard rails to make the sensible the default happy path

Server actions -> anti pattern

Dev & prod Build times -> forever 

New features abstraction above web standards that could be 1:1 mapped

Outside of that and me preferring page router I have no real issue with it. Though using it off of vercel the latency SUCKS!