I'm surprised the author didn't mention the use case where I've seen this most often: animation easing. In every JS library I've seen, the strategy pattern was used for easing functions.
Sorry, but (coming from a 40-years-of-software-development grizzled veteran), I don't see any new pattern here. Just good old-fashioned modularity.<p>Perhaps I missed the point?
Try jQuery Condom, which allows you to make namespaces jQuery Plugins on the fly and override jQuery functionality without touching the global namespace (modularity).<p><a href="https://github.com/kuroir/jQuery-Condom" rel="nofollow">https://github.com/kuroir/jQuery-Condom</a>
Tell me if I have this straight: this pattern basically says to create a generic object with properties and handlers to allow for simple iteration, creation, etc. like you would with an interface. Then, if needed, use a prototype to set defaults?
In Python, at least, this pattern is called the "dispatch dictionary" and relies on the ability of Python to store just about anything as dictionary values. It is considered to be Python's answer to the question, "Why is there no switch/case in Python?"