Released nanomorph, hyper fast DOM diffing for real DOM nodes
-https://github.com/yoshuawuyts/nanomorph …
-
-
Replying to @yoshuawuyts
How does nanomorph perform in uibench? https://localvoid.github.io/uibench/ It would be good to see how it compares to the others.
2 replies 0 retweets 1 like -
Replying to @trueadm @yoshuawuyts
I looked at the source, it seems that you are not handling keys and you're accessing childNodes (childNodes is terribly slow)?
1 reply 0 retweets 0 likes -
Replying to @trueadm
oh interesting - yeah so we're not virtualizing anything; but I think for real-world settings this would turn out to be quite fast
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @trueadm
like: using thunks all the way down creates a Merkle-tree like situation which means updates happen super precisely
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
I'm not so sure. I tried something similar a while back before Inferno and I found it was extremely fragile (e.g. namespaces).
1 reply 0 retweets 0 likes -
Replying to @trueadm
namespaces? Not doing anything like that; or am I missing something. You're not talking SVG are you?
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Yeah, SVG/MathML namespaces was one of the fragile points. There were also others. Performance on mobile wasn't great either.
1 reply 0 retweets 0 likes -
Replying to @trueadm @yoshuawuyts
Anyway, I'm sure you'll find a way around them. Let me know when you have some uibench results up. Would be v.interested to see
1 reply 0 retweets 0 likes
yeah, so that's what I thought too. Not gonna bother diffing, full replace only. Up to users to manage them using a separate engine
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.