Varun Srinivasan
@v
does anyone know of large, authenticated web apps built with nextjs? evaluating for web app
15 replies
0 recast
0 reaction
borodutch
@warpcastadmin.eth
don't use nextjs for the love of god 👀
4 replies
0 recast
0 reaction
Kiren Srinivasan
@kiren
Curious why you feel that way
2 replies
0 recast
0 reaction
borodutch
@warpcastadmin.eth
- as industry we finally realized that users have supercomputers in their hands and we don't want to compute everything centrally with ssr - best case initial load of bundle is ~300kb (bit.ly/3woeAXH) as opposed to ~13kb with preact (bit.ly/3kDNkC5) - we came up with cdn's, use them to serve bundles etc etc etc
2 replies
0 recast
0 reaction
borodutch
@warpcastadmin.eth
but no matter how many logical arguments i'll present developers will still want to make: - bulky slow apps - backend and frontend tightly coupled - unscalable for large number of users (remember the centralized computing with ssr?) - large undocumented unmaintainable codebases that make you write more code
2 replies
0 recast
0 reaction
borodutch
@warpcastadmin.eth
because changing your mindset towards user-oriented benefits is not trendy making yourself look like you do is trendy this is similar to why people use redux instead of valtio and sql instead of nosql when people decide on their code stack they rarely switch but when you switch you're able to pick best
3 replies
0 recast
0 reaction
Elie
@elie
Slow - depends on app. A lot of v fast Next apps. Tight coupling - not really and the DX is great compared to many over complex setups because “separation of concerns” Unscalable - serverless is highly scalable Undocumented/write more - not a property of Nextjs
2 replies
0 recast
0 reaction
