Content
@
0 reply
0 recast
0 reaction
dylan
@dylsteck.eth
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
2 replies
1 recast
4 reactions
dylan
@dylsteck.eth
oops the tag didn’t go through! cc @samuellhuber.eth I think you’re gonna like this one :)
1 reply
0 recast
1 reaction
Samuel ツ
@samuellhuber.eth
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!
1 reply
1 recast
2 reactions
dylan
@dylsteck.eth
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
0 reply
0 recast
2 reactions
