Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

Steve pfp
Steve
@stevedylandev.eth
Devs are waking up πŸͺ– https://youtu.be/zJVyOETKvzQ
4 replies
3 recasts
24 reactions

pugson pfp
pugson
@pugson
$20/mo to not have to do any of this is a great deal
4 replies
0 recast
9 reactions

Steve pfp
Steve
@stevedylandev.eth
Until it's not $20 a month ;) There are plenty of other solutions out there that work way better than this and are still very affordable (i.e. Cloudflare workers or pages). The key imo is using frameworks that have the ability to migrate somewhere else vs Next which is a total lock in
1 reply
0 recast
1 reaction

pugson pfp
pugson
@pugson
next can be deployed to railway at any time. the key is decoupling your backend from serverless functions and using SSR only where it makes sense
2 replies
0 recast
2 reactions

Steve pfp
Steve
@stevedylandev.eth
While you can deploy Next in other contexts, it's never complete and has the full integration that Vercel has with Next. Sure you can limit SSR as much as possible, but you still end up with a messy experience full of bugs (which people do, and hence why OpenNext exists). Why bother when there are way better options out there? I totally understand the appeal of Next.js and Vercel, but imo they're a bundled deal.
1 reply
0 recast
1 reaction

v1rtl pfp
v1rtl
@v1rtl.eth
what's the point of using SSR framework and avoid SSR as much as possible? Just use something that doesn't require you to use SSR at all (TS Router for example) or is full on SSR (like Waku).
1 reply
0 recast
0 reaction