[Bug 27310] Virtual DOM and DOM diff

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27310

vjeuxx@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vjeuxx@gmail.com

--- Comment #3 from vjeuxx@gmail.com ---
Some resources from React you may want to look at while investigating this.

http://facebook.github.io/react/docs/reconciliation.html#problematic-case
https://speakerdeck.com/vjeux/oscon-react-architecture (starting slide 16)

The two big challenges that I haven't seen evoked yet in this thread are:

 - How do you implement the concept of identity when doing the diff. We opted
in for comparing elements pair-by-pair and assume they are identical if they
have the same tag. Or using the `key` attribute to map two elements within a
list.

 - How do you deal with higher order components. One of the critical aspect of
React is that you can nest components. It implies two things: you can do a diff
on partially resolved components and alter the flow of the diff algorithm while
it's running via shouldComponentUpdate.

Also, I would be pretty sad if the API would involve serializing that virtual
DOM into a string to pass it to the browser.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 12 November 2014 17:21:39 UTC