You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
There are two main reasons why React has their own event abstraction, instead of relying on the builtin browser implementation.
Performance. It allows React to re-use event objects, thus not triggering the GC as often.
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).
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/
The text was updated successfully, but these errors were encountered: