In reply to Johnny.

George, the whole point is that Jetpack is making API services out of items which could be executed directly (and even better) from the plugin itself. A Wordpress publisher can just as easily authenticate to Google+, Facebook and Twitter without third party services. Heck we've even created the fastest social services plugin (in private beta on high traffic paid sites) in the world, Pretty Social which does just that with absolutely no need of any intermediate API service.

That's just one example. The same applies to related posts (why doesn't Automattic do some work on efficient semantic indexing and release it to the COMMUNITY under GPL while we're on the subject) . Requiring an API service to submit content to search engines is beyond ridiculous. Any junior programmer could build that into local PHP faster and better than putting it through an external service. Again, why isn't Automattic leading the way with some public code for content distribution?

I picked only a few examples, low hanging fruit. One could take the entire Jetpack apart piece by piece as unnecessary serviceware. As Jetpack belongs to Automattic, unfortunately, the playing field is not level and community objections are steamrolled.

If Automattic wanted to play fair (and it's clear Matt/Jetpack/VC's don't), you'd unbundle Jetpack and let each plugin compete on its own merits. Most of Jetpack would place third or fourth or worse in its respective marketplaces.

I believe you are paid for your time lambasting anyone who voices any objection to Jetpack's borg-like behaviour by Automattic. I'm writing on my free time, so please pardon me the brevity of my reply.