Content
@
0 reply
0 recast
0 reaction
✳️ dcposch
@dcposch.eth
NextJS is bloatware. Multi-minute builds on a tiny site. Baroque additions to the language... put a bare string constant into a file to completely change its behavior. Buggy, try deleting .next & rebuild. Then it edits your package-lock while compiling. How did this become the standard? Deport.
9 replies
7 recasts
48 reactions
Tayyab - d/acc
@tayyab
Overkill is most cases. Serves a purpose if you want offload render lifting to the server. Good for cases like Amazon, Blogs, etc. When there is not a lot of client interaction.
1 reply
2 recasts
8 reactions
Rafi
@rafi
Unfortunately, that's the end game for most ventured back open source dev tools
0 reply
0 recast
2 reactions
Zach
@zachwill
100% agree.
0 reply
0 recast
1 reaction
Ale Machado
@ale
Most JS is bloatware tbh
0 reply
0 recast
1 reaction
Russell Castagnaro
@rcastag
Thank you I couldn’t agree more
0 reply
0 recast
1 reaction
Joel Cares
@joel
Use 11ty
0 reply
0 recast
0 reaction
Nate Maddrey
@nmadd
What do you use instead?
0 reply
0 recast
0 reaction
Vorcigernix aka Adam
@vorcigernix
Well, I started playing with react native and expo and next feels like a walk in a park TBH.
0 reply
0 recast
0 reaction
Ivan Koriakovtcev
@vanya
Vite and right hands do the thing. Nextjs is broken to the roots
0 reply
0 recast
0 reaction
wasyl
@wasyl
Never had problems with Nextjs if you use it properly. Sure its overkill for some use cases and not the solution for everything, but its caching, static gen, and server side rendering with react is useful
0 reply
0 recast
0 reaction
Vlad Plamadeala
@zetroon92
https://t.me/alpha_web3_bot?start=6a4f0f77 DEX
0 reply
0 recast
0 reaction
esposit0 🦊
@esposit0.eth
The only kill feature is SSR out of the box. Overkill, over-complicated and over-opinionated for all the rest. Especially if you’re not planning on deploying to Vercel
0 reply
0 recast
0 reaction
Ivy
@ivy
noooooooooo
0 reply
0 recast
0 reaction
