If you think that @remix_run is coming for you Next.js users... I mean, we'd love to have you as users of Remix and all, but you're not really our target... 
@remix_run Some people (a minority) are reading *way* too much into this. This isn't a jab at next. This is showing that Remix is an evolution of React Router. It was never about competing with Next, it was always about serving our React Router users better.
@remix_run The reason for the download chart is to show what our ambitions are. We have way bigger plans than just to compete with another framework.
In retrospect, the chart could have been left off. This is the perspective I have and I was sharing it. Even though twitter would have you believe that everyone's using Next.js, they're not. So there's 100% room for both of us. We don't plan/have to "take" Next's users to grow.
Literally the *only* reason we made the Next vs Remix post is explained at the top of the post remix.run/blog/remix-vs-… (followed by us gushing over how great we think the team over at Vercel is).
We didn't want to talk about Next.js, but everyone asked about it.
We didn't want to talk about Next.js, but everyone asked about it.
I shared the chart and comparison in the original tweet because I'm subtweeting people's assumptions that we're coming after Next.js users. We're not targeting Next users. They're welcome to join us, but we're targeting React Router users. 🤷♂️
• • •
Missing some Tweet in this thread? You can try to
force a refresh
