- 
                Notifications
    You must be signed in to change notification settings 
- Fork 45
perf: improve performance #113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 perhaps someone from undefined-team should sign off the UI part of this PR.
It looks good to me, yet I shouldn't be the one deciding whether you're dropping certain mosaic components or not. However as an external person, I'd say it's a reasonable choice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't able to detect any visual regressions, so I believe this is ok!
| 🎉 This PR is included in version 4.0.0-beta.4 🎉 The release is available on: Your semantic-release bot 📦🚀 | 
| 🎉 This PR is included in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 | 
Times in parenthesis are mounting times of the 2x-stress schema story in Storybook.
SchemaRowand beyond (1590ms -> 850ms)The problem with mosaic components is that for almost 0 gain (beyond type-checking of style-props), you render yet another element, and especially yet another
forwardRef-ed element, both of which eat up performance as you scale.