provides simple mechanism to support using cached nodes

[AutoSponge]

also supports nodes that get augmented outside of the morphdom render cycle
closes #77

[yoshuawuyts]

I like the efficiency of the implementation, but I wonder though if it's a good idea to make this rely on non-native DOM methods. I think it might be worth it as there's little drawback, but I feel we should definitely ponder if this is the way we want to go.

[AutoSponge]

@yoshuawuyts isSameNode is a native method. Was there another method you were referring to?

EDIT: I guess, the need to polyfill that method for other browsers becomes either a job for morphdom or an exercise for the implementer

[yoshuawuyts]

@AutoSponge woah, I had no idea. This is great 💯

[AutoSponge]

I will still put in a check so it doesn't blow up in IE7-8.

[yoshuawuyts]

YESSSSS! 🎉

[patrick-steele-idem]

Thanks for the improvement! I will be including this release that will go out soon. I'm also working on some performance improvements and am also working on adding support for diffing the real DOM with a virtual DOM (that implements the same API as the real DOM). Thanks, again.

[yoshuawuyts]

@patrick-steele-idem when do you expect the release to come out? Lots of folks upstream are super stoked to start using this 😁

[patrick-steele-idem]

@yoshuawuyts Sorry, I became super focused on benchmarking and optimizing. I promise I will publish by EOD today.

[patrick-steele-idem]

Alright, new version published with support for isSameNode and diffing with virtual DOM nodes: [email protected]

Please let me know if you see any issues. Thanks!