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.

Sign up for GitHub

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

Jump to bottom

alternatives/validation to async batching updates #9

Closed

threepointone opened this issue Jul 24, 2016 · 1 comment

Owner

threepointone commented Jul 24, 2016 •

edited

Loading

I'm unwilling to async-ify the application of styles like aphrodite, but I'm willing to figure out alternatives -

is this a real issue? can we benchmark it?
how much pressure is released by server side rendering/bootstrapping?
how much does hashing help?
can static opts help? (possible static optimizations #2)
can we hook into react's batching mechanism?
if insertRule() has better perf (despite bad dx can't edit css in devtools(!) #8), can we use that in prod instead?

The text was updated successfully, but these errors were encountered:

Owner Author

threepointone commented Jul 31, 2016

Closing this, solved well with insertRule in production +SSR when needed. Further optimizations as there discovered.

threepointone closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment