Earlier quoted context omitted.
>By the way, virtual-dom is a little bit early to use for production application. For example, if you have some elements in your vdom, that are changing after you render it (i.e. like buttons, embeded posts, etc.), virtual-dom will be totally confused and unpredictable. On the one hand, yes, and on the other hand, I have never in practice had this happen when it was not my fault. I've also never had it be my fault un…
For example, embedded FB post. In React you can deal with it using componentShouldUpdate and others. I don't know how to deal with it in virtual-dom (package), without going deep into patching algorithm.
Ah, my mistake. I didn't realize the distinction there. Makes more sense now.