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
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
Samuel ツ
@samuellhuber.eth
https://opennext.js.org/ though I'd just use React Router 7 if you want the NextJS experience but with better patterns. SolidStart (SolidJS) if you care about state management or SvelteKit if you wanna get outside of something that looks like React (Solid is not react, but looks similar which I like personally). Astro for content pages (likely good for fullstack too, but haven't tried) And then if you care even more just ping @darrylyeo and you'll get more options then you can process (at least then I can lol)
2 replies
1 recast
3 reactions
