Skip to content
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

benchmarks and understanding trade-offs: implications of removing the vdom #27

Open
davidmarkclements opened this issue Apr 8, 2019 · 1 comment

Comments

@davidmarkclements
Copy link

davidmarkclements commented Apr 8, 2019

Am I right in thinking that the main trade off here is removing React's vdom in favour of package size?

If so, is this now acceptable because modern browser DOM implementations are significantly faster than when react was released? Or is it more that it depends on the type of application?

For instance would an app with very frequent updates still benefit more from the vdom than lower package size?

Are there any publicly available benchmarks for testing rawact vs react in different scenarios?

@ryansolid
Copy link

This is a decent benchmark on some list operations. https://github.com/krausest/js-framework-benchmark. Gives you an idea. The VDOM vs non-VDOM thing is probably mostly for size, but it doesn't have to be. React is not particularly groundbreaking for performance, so it's fairly trivial to take any approach and make it outperform React. But performance isn't why you choose React.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants