---
title: "Comment by Dávid Szabó on \"Re-evaluating Next.js: Did it go the wrong path?\" | Hashnode"
description: "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 a"
url: "https://hashnode.com/posts/re-evaluating-nextjs-did-it-go-the-wrong-path/65f8145981fd393af03fe62a/comment/65fbdbbfbd4a90d90edf7bca"
---

[Discussion](https://hashnode.com/posts/re-evaluating-nextjs-did-it-go-the-wrong-path/65f8145981fd393af03fe62a)

Comment [Re-evaluating Next.js: Did it go the wrong path?](https://hashnode.com/posts/re-evaluating-nextjs-did-it-go-the-wrong-path/65f8145981fd393af03fe62a)

[Dávid Szabó](https://hashnode.com/@davidszabo)

[Mar 21, 2024](https://hashnode.com/posts/re-evaluating-nextjs-did-it-go-the-wrong-path/65f8145981fd393af03fe62a/comment/65fbdbbfbd4a90d90edf7bca)

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.

[David Lorenz](https://hashnode.com/@activenode)

[Mar 22, 2024](https://hashnode.com/posts/re-evaluating-nextjs-did-it-go-the-wrong-path/65f8145981fd393af03fe62a/comment/65fbdbbfbd4a90d90edf7bca#reply-65fd4f3c57238eb7113b5cb9)

Thanks for sharing your experience!
