In reply to Justin Tadlock.

OK, thanks for the heads-up Justin.

However, that doesn't remove the fact I need to download dozens of average, me-to modules, which I don't need, and don't want, in order to get to the one or two I might find useful.

What would make much more sense from the end-user viewpoint is that, if JetPack was a framework, and each module was released as an individual plugin module, I could download separately, everyone's Jetpack could be smaller, just what they wanted and contain different modules to everyone elses installation.

In fact, as a successful framework, Jetpack would almost certainly attract other authors to create even better replacement modules for it, using the Jetpack framework/infrastructure model.

Then we'd find out what's really wanted, what's needed and what's good or bad, instead of mashing it all together. I suspect that won't ever get done though, because most of the modules just aren't capable of making it on their own.

Bundling loads of average plugins together doesn't make them better, it just makes it a bigger download.

I think Jetpack a wrong-headed and inelegant solution to a WordPress problem, not an end-user problem. Hopefully, by version 4 or 5 Jetpack will morph into this framework version I am imagining.