When (and Why) to Stick With React — Even If Solid Looks Better
There’s no denying it: Solid is better than React in several technical aspects. It boasts fine-grained reactivity, smaller bundle sizes, and better runtime performance out of the box. If you compare benchmarks, Solid almost always comes out ahead.
But here’s the catch: being technically better does not automatically mean it’s the right choice. Especially if you’re an independent consultant who thrives by working with many different companies.
Why I Stick With React (For Now)
- React Still Dominates
Despite the rise of newer frameworks, React continues to dominate the frontend ecosystem. Most companies already have React projects in production, and most job postings still list React as a requirement. - The Ecosystem Advantage
With React, you get access to a massive library ecosystem, endless tutorials, Stack Overflow answers, and third-party tooling. That ecosystem shortens delivery time for client projects. - Marketability as a Consultant
My value lies in being able to adapt quickly to a client’s stack. Since React is still the most common denominator, being fluent in React means I can walk into more companies without friction. - Enterprise Stability
Enterprises are cautious. They don’t jump onto the newest shiny tech unless it’s proven. React, backed by Meta, gives them confidence. Solid, while exciting, doesn’t yet have the same level of corporate trust. - Risk vs. Reward
Switching to Solid now would give me personal satisfaction and early adopter credibility. But it wouldn’t significantly increase my client opportunities. From a business perspective, the reward doesn’t outweigh the risk.
What Could Make Me Switch
I’m not emotionally tied to React. If the market shifts, I’ll happily switch. Here are the signals I watch for:
- Hiring Trends: When job boards start showing more demand for Solid (or another framework) than React, that’s a clear sign.
- Enterprise Adoption: If larger companies start standardizing on Solid (not just hobby projects or startups), the tide is turning.
- Ecosystem Maturity: More libraries, stable tooling, and strong community support.
- Developer Preference Momentum: If more developers start advocating Solid in conferences, blogs, and open-source contributions, it’s a leading indicator.
Until those signs are visible, React remains the pragmatic choice.
Other Considerations
- Learning Curve for Teams
Many developers already know React. Training costs are lower, onboarding is easier. Switching frameworks introduces friction. - Integration With Legacy Systems
Many companies have existing React codebases. Even if Solid is chosen for new work, they’ll still need React talent for the old systems. - Client Psychology
Sometimes the framework you use is less about tech and more about client comfort. A CTO might feel safer choosing React simply because “everyone else uses it.” - Long-Term Flexibility
Staying sharp in React doesn’t stop me from dabbling in Solid or other frameworks. It just means I’m strategically choosing where to invest most of my professional time.
The Consultant’s Mindset
At the end of the day, my job is to deliver value to clients quickly and reliably. For that, I prioritize popularity and ecosystem stability over raw technical elegance.
If I were building a personal project where I had complete control, maybe I’d use Solid today. But as a consultant working with diverse clients, React is still the safer, more profitable bet.
And when React eventually stops winning? That’s when I’ll happily switch. Until then, I’ll keep my ear to the ground, stay aware of the alternatives, and continue to ride React’s dominance.
Comments ()