Is stitches still under maintenance?? #1026
Comments
|
I would recommend to look at the solutions that already support static extraction, like Vanilla Extract. Runtime libs are still fine and they still are incredibly useful to ship features faster, but I think whole React community is not really interested in making sure they work well with all streaming stuff. |
|
After @peduarte left modulz, stitches and radix have been given much less attention. He was a really great communicator for the project and did a fantastic job in responding to issues + community outreach. Since he left, it feels like stitches and radix has been forgotten and left on the backburner. I think that stitches and radix are beautifully designed and the best libraries in the react ecosystem, and I personally feel that it does them a huge disservice for these libraries to be left in such a state. Hopefully, someone can take on the role that @peduarte left and revitalize these two projects. |
@cpakken to respect the remaining team members, if you are referring to the Radix Primitives, they were coded by @benoitgrelard, @andy-hook and myself. I have since left but they are still working hard on them so the primitives are very much alive. You only need to check the repo and you will see frequent progress. They are also frequently helping in discord. I cannot help re:stitches tho. |
|
@cpakken @jjenzz thanks you all. @LexSwed I saw that reference about CSS-in-JS.. Do you really think that is something that will disappear from React eco-system?? |
|
I don't think that's a fair comment @cpakken. It's fair with regard to Stitches, it hasn't been getting much attention over the past few months. But @benoitgrelard and @andy-hook are working full-time on Radix, the repo activity is the healthiest it's ever been, and they both help out in Discord frequently. We're working towards a v1 launch soon. |
Oi no. There's unimaginable amount of value shipped to the users by developers who feel more productive with css-in-js solutions. I don't think it will disappear any time soon. The fact that it's not the best approach for the end users doesn't mean they get less value. And that's what important. |
|
Thanks for clarifying the status of Radix primitives. I'm very glad to hear that the project is actively being worked on. As a fan of the project, I check https://www.radix-ui.com/docs/primitives/overview/releases from time to time and my misunderstanding regarding Radix was because I noticed there were no new releases since the end of February. I thought this coincided with the lack of activity in stitches and drew connections where there were not. Sorry 😓 |
|
You can follow the milestones progress here too: https://github.com/radix-ui/primitives/milestones. You can even take a peek at all the documentation changes (including the release notes) for the upcoming changes so far: |
|
No prob at all @cpakken. Easy mistake to make. All the ❤️ |
So do you recommend us to pick stitches for our project? I didn't see topics that related to stitches there... |
|
The React team recommend people use static CSS solutions rather than runtime CSS-in-JS solutions. Here is a GH discussion. More info in this Twitter thread. Stitches is a runtime lib, so it's not currently a lib that the React team would recommend. Furthermore, Stitches is not compatible with React 18's streaming feature. If you don't plan to use streaming, then we consider Stitches v1 stable, and it should work fine for your project. If on the other hand, you want to "future-proof" your project, and remain aligned with the general direction of the industry, you might want to consider a static solution instead. We have explored a static version of Stitches, which uses the same API, but we have not yet committed to completing and shipping it. |
|
@colmtuite I think CSS-in-JS is a good choice for UI libraries because it makes it very easy to tree-shake unnecessary styles and customize it. In case of static extraction, the end users would need to include either one big CSS file which includes all the styles or include separate files of each component they use which is not the best DX. It possible to write plugins for build tools but it's hard because of big amount of tools and it also requires some addional setup. I wouldn't consider Stitches v1 stable because of some issues which makes it hard to use in a lot of cases:
I undertand that you have a different vision about it but Stitches became popular very quickly and it already has quite a lot users. So if you don't plan to maintain it then you can at least find maintainers from a community which I think will be easy. |
|
@colmtuite With your thoughts on static css being more future-proof, is modulz.app still using stitches to style its UI? If not what is your team using? |
|
@cpakken Yes all of our apps (including Radix docs/site, Stitches docs/site, Modulz app, Modulz site, admin apps etc.) use our design system, which is built on Stitches v1. That's not too relevant though imo. My point above is that the React team (and the broader front-end community too imo) is not in favour of runtime styling solutions. The general direction things are headed is towards styling solutions that don't have any runtime cost. So if you want to make a "future-proof" decision, that is the data point to track. What any one company is currently doing is almost irrelevant. |
|
Please don't forget that stitches is not only about React. Its bad for people using |
|
Stitches is really thoughtfully designed I hope the project survives |
I want to use
stitchesand want to make sure that stitches are still under maintenance & process...The text was updated successfully, but these errors were encountered: