[joy-ui] Temperature check on the future of Joy UI
Open
@siriwatknp is already working on this.
Since Jun 24, 2024.
docs
package: joy-ui
RFC
scope: all components
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
What's the problem?
I'm tempted by Joy UI for a greenfield project, but I'm a bit worried about whether it's a dead end or not. I totally understand putting it on pause to focus on other projects. What I'm wondering is - now that you've had some time - do you think you'll still go back to Joy-UI development when that's done? Or would you recommend sticking with MUI for the time being?
I'm more concerned with longevity than the look & feel, though the look & feel of Joy UI is probably a better fit for this particular application.
What are the requirements?
No response
What are our options?
No response
Proposed solution
No response
Resources and benchmarks
No response
Search keywords:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.