My FeedDiscussionsHeadless CMS
New
Sign in
Log inSign up
Learn more about Hashnode Headless CMSHashnode Headless CMS
Collaborate seamlessly with Hashnode Headless CMS for Enterprise.
Upgrade ✨Learn more
David Lorenz

19 likes

·

3.7K reads

4 comments

Dávid Szabó
Dávid Szabó
Mar 21, 2024

The caching problem alone was a dealbreaker for us. We built a proof-of-concept in Qwik, Next.js, and Remix. So far, we have had the best experience with Qwik and Remix, but we wanted something closer to Next.js, so we went with Remix.

Next.js feels too corporate nowadays. They are pushing their ideas, and I feel like they keep ignoring the community (their users). The caching issue is a perfect example for this.

7
·
·1 reply
David Lorenz
David Lorenz
Author
·Mar 22, 2024

Thanks for sharing your experience!

·
Livian Bern
Livian Bern
Mar 22, 2024

wow

·
Viktor Lázár
Viktor Lázár
Mar 25, 2024

The issue, as you mentioned in your conclusion, is that Next.js should not be used for every type of app. Next.js targets the most common websites, not exotic web apps. Communication around any related topics, either by Vercel or the React core team, is a real issue. Next.js also doesn't really guide developers, creating misunderstandings and mistakes in how devs use it. However, it's worth noting that they are trying very hard to improve it. The state of Next.js 13 was awful, but it's much better nowadays. It's not just challenging for the average developer, but also for the framework creators too.

·