Tony Quetano

@FlynnLeeGit, just add an object version of the same benchmark that exists. It will surprise how much the performance drops when real serialization needs to occur.

creator of moize here, figured I'd chime in. I crafted my words carefully when writing my README. In benchmarks on my various machines (an old laptop, my work desktop, and...

I'm not saying those invalidate my benchmarks, far from it ... but your question and follow-up statement appears to believe in the concept of a definitive answer, and I was...

@caiogondim thanks, always nice to find someone that likes to work together instead of complete. :smile_cat: I can say that the biggest optimization is in the caching mechanism used. I...

@dantman no disagreement, it's about the best tool for the job. The serialization technique `fast-memoize` uses does have use cases, which is why I kept a serialize option for `moize`...

@dantman for bias toward recency. Memoizers that have a cache of caches, like those being discussed, bias towards most recent calls because the expectation of a memoized function is that...

@dantman I don't want to derail this thread. Originally you talked about needing to use multiple libraries because they need different kinds of memoization, and the point I was getting...

The problem is that the traversal order discussed in that article is not for all object traversals period. There is no universal order expectation for how objects will display, however...

Add how many browsers have actually implemented the spec? There is a practicality piece in here, as implementing a custom serializer instead of leveraging JSON.stringify as the default will cause...

I can definitely look into this, but it may take a minute. Is there a way you can provide a simple repro of the issue?