Choosing a React Framework
Is their a guide or advice for choosing a React Framework
I’ve been listening to the podcast which seems very opinionated about front end approaches and keeping it simple. However I’m new to React and it’s difficult to know the pluses and minuses of different frameworks
8 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
React has wide community support as it is still the most used frontend framework hence Convex has the best support for React. If you are new to React and Convex, the best is to stick to these well supported and widely used combination because whenever you have issues which cannot be resolved by ChatGPT, you will have better chance to find support in these communities.
(I recommend using React with Convex as a big fan of Svelte.)
The "it" in "keeping it simple" is different for everyone. If you don't know which framework to use at all, then your tightest bottleneck is understanding front end dev in the first place.
Probably Next.js would be the overall simplest because it currently has the largest ecosystem, community, and docs, despite requiring more complicated code.
This is what I was wondering should I use next.js
I’ve done a little with Next.js and with vite
Is there a link or article to help with these decisions
There are articles describing the technical differences. But if you don't have the prerequisite knowledge to comprehend the technical differences, then they aren't that helpful.
a beginner would need to piece together a prelimanary tech stack and check for compatibility.
You can use non-technical heuristics like going to each piece of your tech stack's communities and seeing what gets built and what people talk about
I'll drop my 2 cents to give a bit of a framework. Since this is all just an opinions.
1. Next.js has wide adoption so there is a lot of help out there. It's downside is that it can feel overdone with a lot of different ways to do similar sounding things. When I've used it my small projects I just use it for the router and do client side everything and connect to Convex. It's just simpler for me to think that way, and I avoid all the strangeness of middlewares, runtimes, ssr etc.
2. Remix/React Router is pretty popular and has a decent amount of adoption. I haven't used this personally used it. But my very limited understanding is that it has fundamentally the same features as Next but it's just a bit simpler in most ways.
3. TanStack Router: Is really well designed, but is a little different than the rest and only has been around for a year or two. But if you're using just Router than you can happily stay in the client only app world. It's particularly helpful if you have complicated routes with custom views etc. The TanStack Start framework that brings all the server side rendering stuff that builds on TanStack Router is still alpha, but looks really promising, Convex team is broadly very excited about it.
If I were you I would just choose something and move on. It's not that important if you start. If you learn more about the technical debt you can come back and revisit this and maybe choose another framework, but nowadays every framework is copying the stuff from the other framework, so they are basically the same.
I’ll stick with Next.js for now