Yes, agreed, using chained prototypes to accomplish nested state charts is not something I'd want to inherit as a maintainer.

It's cute, in a "look at how I can make the language do this"/novelty way, but I don't think it's JavaScript's fault per se, as this seems similar to Java architects solving problems with "just another factory", "just another annotation", "just another bytecode generator", etc.