Content
@
https://warpcast.com/~/channel/devfc
0 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
NextJS outside of Vercel is an anti pattern. Server Actions in general are too. NextJS can be good tech, but doesn't make you use it as good tech by default. Constraints are good. Make it hard to do the bad things >>> make everything easy. NextJS tries making everything easy and therefore makes shit hard if you aren't on the happy path. That's why some of you may have noticed I am not the biggest next fan. It's not Next. It's how next usually is used. And yes we run production apps on Next on vercel. We don't otuside of Vercel though. Anything outside Vercel you'll almost never see me advocate for NextJS. Tried that e.g. with Frames. Post Routes went from 200ms response times on vercel to 2s response times and yes I was geographically very very close to the VPS running the NextJS instance and it had 16 cores, 64GB ram so definitely not network & hardware limited!
8 replies
2 recasts
19 reactions
dylan
@dylsteck.eth
two things i'll say: - not a big fan of server actions, big anti pattern especially when not implemented properly(similar to how not *properly* using RSCs can make your app slow) - vercel launched a RFC for a new version of the official deployment adapters api with the goal of making deploying nextjs on non-vercel platforms better https://github.com/vercel/next.js/discussions/77740
1 reply
0 recast
0 reaction
dylan
@dylsteck.eth
not saying this to say i love all things nextjs/vercel, but it does seem like they're putting in a lot of work to fight conventional narratives/devex pain points
1 reply
0 recast
0 reaction
