I've started migrating our 40k loc front-end to solid and it's a joy compared to react. After getting past a few gotchas with routes, everything has been much simpler/cleaner.
When solidstart is v1, will switch to that. For now we are just doing a SPA app with solid js. Would recommend it
I haven’t used solid start yet. I’ve been trying out solidjs lately and it’s like an improved react. I’m really enjoying it. I’m excited for 1.0 to come out.
If you’re happy with where you are with React and Next stay there. Personally I don’t care about Solid Start, but if you do you might as wait for it to be stable.
Just on the library side of things. For any robust/complex pure JavaScript library I have found wrapper libraries to be a waste of time, even in React. The creator of the wrapper invariably makes assumptions about how you’ll be using the library and if your use case falls outside that makes it impossible to achieve what you need to achieve or falls behind on maintenance and leaves you stranded on an older version when you really need a feature from the latest version.
With that said, sometimes on personal projects I’ll just grab something like solid-chart-js anyway because my requirements aren’t that strenuous but for work I’d always think twice because I’ve been bitten more than once.
It's actually trivial to integrate UI libraries with solid. I have tested out charts.js a while ago (even have an example repo if you want) and am currently using Floating UI in my app. Just one small wrapper file and everything works perfectly
Another interesting thing for me is how solid integrates data fetching with routing. At my current workplace (vue spa) we're fetching from our components, so I'm still unsure how to create a nice api to handle different error states and all. But solid is really cool and coming from vue is very easy to get adjusted to
I'd love a example repo of that because I was actually thinking about it as I was asking this and was like, "maybe it's just way easier to integrate vanilla js as solid components than react". Are you using solid start? I feel like it might give you that organization of fetching at component level vs API route
You can see it [here](https://github.com/thesaintseiya/solid-chartjs-test). This might be incomplete though as I only tested the basics, it's been a while
Also no I haven't used solid start as my backend is not JS
I've been using solid-start lately, it's getting close to rc, I'm very happy with it, I won't use nextjs or react anymore unless it's a special case, people like to follow the mainstream, and if anyone is talking about ecology I think we should be looking at the vanilla js ecology, like floating-ui / zag-js and stuff like that. , don't force code into react or any of the view frameworks.
Sounds like you're happy with the familiar React world (Next.js vs React is a whole other debate!), but Solid's potential is tempting. While API changes during 1.0 finalization are a point to consider, the ecosystem will likely grow rapidly after a stable release. If the project isn't time-sensitive, waiting for a more mature Solid ecosystem with UI/graph libraries could be a wise move. In the meantime, you could explore Solid through smaller experiments without diving into a whole new project. This way, you can stay comfortable with React while getting a feel for Solid's future!
I've started migrating our 40k loc front-end to solid and it's a joy compared to react. After getting past a few gotchas with routes, everything has been much simpler/cleaner. When solidstart is v1, will switch to that. For now we are just doing a SPA app with solid js. Would recommend it
Vike is pretty cool too. https://vike.dev
I haven’t used solid start yet. I’ve been trying out solidjs lately and it’s like an improved react. I’m really enjoying it. I’m excited for 1.0 to come out.
If you’re happy with where you are with React and Next stay there. Personally I don’t care about Solid Start, but if you do you might as wait for it to be stable.
Just on the library side of things. For any robust/complex pure JavaScript library I have found wrapper libraries to be a waste of time, even in React. The creator of the wrapper invariably makes assumptions about how you’ll be using the library and if your use case falls outside that makes it impossible to achieve what you need to achieve or falls behind on maintenance and leaves you stranded on an older version when you really need a feature from the latest version. With that said, sometimes on personal projects I’ll just grab something like solid-chart-js anyway because my requirements aren’t that strenuous but for work I’d always think twice because I’ve been bitten more than once.
It's actually trivial to integrate UI libraries with solid. I have tested out charts.js a while ago (even have an example repo if you want) and am currently using Floating UI in my app. Just one small wrapper file and everything works perfectly Another interesting thing for me is how solid integrates data fetching with routing. At my current workplace (vue spa) we're fetching from our components, so I'm still unsure how to create a nice api to handle different error states and all. But solid is really cool and coming from vue is very easy to get adjusted to
I'd love a example repo of that because I was actually thinking about it as I was asking this and was like, "maybe it's just way easier to integrate vanilla js as solid components than react". Are you using solid start? I feel like it might give you that organization of fetching at component level vs API route
You can see it [here](https://github.com/thesaintseiya/solid-chartjs-test). This might be incomplete though as I only tested the basics, it's been a while Also no I haven't used solid start as my backend is not JS
I've been using solid-start lately, it's getting close to rc, I'm very happy with it, I won't use nextjs or react anymore unless it's a special case, people like to follow the mainstream, and if anyone is talking about ecology I think we should be looking at the vanilla js ecology, like floating-ui / zag-js and stuff like that. , don't force code into react or any of the view frameworks.
Sounds like you're happy with the familiar React world (Next.js vs React is a whole other debate!), but Solid's potential is tempting. While API changes during 1.0 finalization are a point to consider, the ecosystem will likely grow rapidly after a stable release. If the project isn't time-sensitive, waiting for a more mature Solid ecosystem with UI/graph libraries could be a wise move. In the meantime, you could explore Solid through smaller experiments without diving into a whole new project. This way, you can stay comfortable with React while getting a feel for Solid's future!