Content
@
0 reply
0 recast
0 reaction
Alex Loukissas 🍉
@futureartist
Not wrong (with current state of nextjs) https://twitter.com/jayair/status/1724107151088513339
3 replies
0 recast
1 reaction
max
@maxmandia
skill issue
1 reply
0 recast
0 reaction
Alex Loukissas 🍉
@futureartist
low effort reply
1 reply
0 recast
0 reaction
max
@maxmandia
low effort quote ;)
1 reply
0 recast
0 reaction
Alex Loukissas 🍉
@futureartist
Touche! But having been thru nextjs since v10 and other frameworks (mostly phoenix) and k8s, I partially agree with the quote here. IMO remix has been doing a better job here.
1 reply
0 recast
0 reaction
max
@maxmandia
which parts of next have been turning you off? sincere question
1 reply
0 recast
0 reaction
Alex Loukissas 🍉
@futureartist
Overall, it seems to me that they are quick to ship beta-level releases (even when it is a v13 product). When things work, they work kind of well. But beyond the basic TODO app demo, we have seen a death by 1000 paper cuts. We have mapped those to existing issues on their github, where many folks are seeing the same.
2 replies
0 recast
0 reaction
max
@maxmandia
sorry this got buried in notis but I think it’s a fair point! I tend to look at it from a different angle; devs weren’t forced in adopting these new, albeit beta, changes from their new releases and instead could at their own will. I have a great amount of respect for how quickly they move :)
1 reply
0 recast
0 reaction
max
@maxmandia
2/2 I just wished they followed Stripes lead in creating incredible documentation for some of the newer features being pushed out - although it’s a hard act to follow. regardless, it’s room for improvement
0 reply
0 recast
0 reaction
