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

Benchmark vs. React #11

Open
hakunin opened this issue Jul 29, 2017 · 1 comment
Open

Benchmark vs. React #11

hakunin opened this issue Jul 29, 2017 · 1 comment

Comments

@hakunin
Copy link

hakunin commented Jul 29, 2017

Hi,
I am trying to figure out if I can do a beanchmark of Domafic to compare performance with React in case of a huge amount of items.

Before I dive into the code, it would only make sense to compare apples to apples, so I'd like to know:

  • Does Domafic do dom diffing and reconciliation like React?
  • Does it do caching based on the input for component (does it even have components?) like React?

I could make the React app not do any caching, but it wouldn't be a very reasonable comparison since in production you want as much caching as possible.

@cramertj
Copy link
Owner

cramertj commented Aug 1, 2017

Domafic does do DOM diffing, but it does not have any caching based on input. The equivalent to a React component is either a DomNode or a function that produces a DomNode, depending on how you look at it. It would certainly be possible to implement some kind of caching, but I haven't done so personally.

Let me know what you discover-- I wouldn't be surprised if React is faster to start out with, but it'd be interesting to see which sorts of UI changes React handles better, since that'd tell us specifically what areas we need to optimize.

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