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

Events Suggestion #1

Open
ericharding opened this issue Oct 26, 2017 · 1 comment
Open

Events Suggestion #1

ericharding opened this issue Oct 26, 2017 · 1 comment

Comments

@ericharding
Copy link

I came across this old article about the react diff algorithm. It seems like they had some trouble with DOM events and instead of attaching events at each level they attach a top level event and manually route the event to the right handler from the virtual tree. I don't know a lot about Xamarin forms but I think this would work in WPF.

https://calendar.perfplanet.com/2013/diff/

@robinheghan
Copy link

robinheghan commented Nov 4, 2017

There are two main reasons why React has their own event abstraction, instead of relying on the builtin browser implementation.

  1. Performance. It allows React to re-use event objects, thus not triggering the GC as often.
  2. Stability. Events work the same across browsers.

I don't think such an abstraction would be as useful in a Xamarin.Forms based world (I'm not even convinced that it's that useful in the browser world either).

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