In reply to mark k..

@Ron, I never hidden my dislike of the concept of jetpack. I am not hating it, (why should anyone hate a software?) I didn't even think about commenting here if sam didn't say that after discovering such a bug that "everything is just great".

Jetpack is not unique in the wordpress eco-system it is just the "king of the hill" when you measure bloat. Same thing probably can be said about "better security", some of the complex themes and many more.

Wordpress runs on a server, it almost never being ran as a vanila install but have plugins, themes and some hacks applied to it, and as such the admin has to be able to "own" the code. The more code there is the harder it is to own it, and the "nice" thing about server code is that just because some execution paths seem to be inactive doesn't mean they can not be triggered by a well crafted request.

The less code you have the easier it is to identify and fix bugs, as simple as that.

Now if you use 50% of the jetpack modules, then sure just use the whole thing, but neither of its features are "best in class", and since they always add new ones, I assume no one uses so many feature of the plugin.

Then there is the cost of upgrades. In properly managed sites no one just upgrades a plugin directly on production and first they test the upgrade on staging. How much time is being wasted now all over the world because of a feature that is not even relevant to the site? And in properly maintained site the push from wordpress.org just do not work as no one will let a web server to write into its plugins directory.

And as evident by the posts on the tavern about the next bug release for jetpack, it is not like anyone can claim that it is a perfect piece of software you can just trust.