yangmillstheory

yeah, i should probably change that tonight

Thanks. I was writing an application that had unrelated components that all acted like view models.

I looked at existing mixin libraries, but found some that either injected themselves into the prototype chain or patched Function.prototype to let mixees customize behavior. I didn't like that, so I thought of this approach.

The rest has been a continuous process of simplification, but I never got back to writing that old application :).

Thanks for sharing! Have you studied aspect-oriented programming formally?

I used the term "aspect-oriented" because a co-worker mentioned it and it seemed appropriate, but I don't have a deep understanding of that philosophy.

I'll take a look at your code, blog posts, and videos later when I get out of work. :)

I you look at the demo site again, I made the chunk size and delay user-configurable, and I'm displaying the current running code.

The API exposes the chunk/delay parameters as options, so it's definitely possible.

If you mean having the library code "learn" the optimal chunk/delay for a given run, that's possible too, but I'd have to wonder about alternative solutions at that point.

It works - and that's the core of what's being done if you look at the code. I just wanted to make something re-usable, configurable, and play around with ES6 generators :).

Thanks for the reply! I was just thinking I should have that on by default.

I'll add an explanation of what's happening.