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
Justin Hunter
@polluterofminds
Next.js is vendor lock-in
1 reply
0 recast
10 reactions
Hoot 🎩
@owl
I remember that netlify was leading an effort to have good support to host next outside of vercel. Was supposed to support their platform and cloudflare workers. Wonder how that is going
1 reply
0 recast
1 reaction
Fots
@fots
to be honest, i heard first time about this issue. what version of nextjs do you use in your projects? i found almost the same thread as you described on the github: https://github.com/vercel/next.js/discussions/58676?utm_source=chatgpt.com maybe that is the case?
1 reply
0 recast
0 reaction
mic0
@mic0
Agreed. I gave up on using it for statically generated content and switched to better alternatives. Its a bloaty overkill framework imo and i wish it werent so prevalent.
0 reply
0 recast
1 reaction
Mo
@meb
I dunno, shipped next js on AWS and Heroku, and was super simple once I had figured out the CI. The issue is more that vercel makes it so easy for non devops-experienced users to deploy to vercel. That said, got into Remix recently and really enjoying it. Way lighter and still gets job done. I like that I can have a full on page + GET and POST in one file, handy for demos
0 reply
0 recast
0 reaction
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
Shomari
@shomari.eth
100% agree with the "forced" lock-in to Vercel (although Netlify performs nearly as well) i MUCH prefer Vue over React so I'm a BIG fan of Nuxt I'm curious, what alternatives exist to NextJS in the world of React? 🤔 (and preferably ones that support Edge networks like cf workers)
0 reply
0 recast
0 reaction
David Hurley
@hurls
This could be because of a cold start maybe? I feel like it should be faster. I'm biased though, I only use Next on Vercel. What setup would you recommend?
0 reply
0 recast
0 reaction
