2011/6/7 Leo Koppelkamm <diebuche(a)gmail.com>om>:
There's usually some code (general utility
fn's, some legacy remappings etc.) in common.js that could break a lot of stuff if
missing. +1 on moving optional stuff to gadgets
It depends on project. General utility functions should be available
as modules, which can be loaded when there is such need (as a
dependency to a gadget or by user/script explicitly). It makes easier
to port gadget to other projects and maintain them, when its
dependencies are well defined, so all changes can be easily tracked.
Separate modules can be directly imported, which is impossible with
overbloated MediaWiki:Common.js.
Yes, it does depend on the project, but I'm pretty sure that in most
projects there are some chunks of js in Common.js that simply should
not be disabled.