Popular this week 🔥
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
We can use Shuttle.rs as backend for Next.js apps and it also includes infrastructure files features integrated in it
5