Unfortunately we live in an imperfect world and the JS infrastructure in Moodle has been changing faster than many of us would like (and certainly faster than our code keeps up with ). But, if we are to try and keep pace with our technical debt, it does make sense to set restrictions for new code to ensure we are vaguely moving forward.
So what do you think our policy should be? Should we prevent new code landing to Moodle core now which isn't using the module support?
My initial thought is that we should acknowledge the amount of code out there and the problems with our rapidly changing landscape by allowing YUI modules for this release (3.0) only. Give everyone whos got some working YUI code nearly ready to integrate to get it in - then prohibit new code landing to core from 3.1 onwards. Of course it'd still be preferred to avoid new YUI code landing, but perhaps there is a case for some flexibility here?