Yup, deactivating modules is a bit of a nuisance at the moment. Which is why we've been working on a new modules screen -- still incomplete, but we hope to have it finalized by the end of the year. You can try our offering alongside the other here:

https://github.com/georgestephanis/jetpack-modules

It loads all the module data into Backbone and rebuilds the table on the fly based on the filtering selected above. It currently has a `cards` view and a `list-table` view -- cards (spiritual successor to the current) is the default, but just append `&list_table=on` to the URL to try it with that view.

If you'd rather just have an easier way to deactivate modules, though, give this one a spin:

https://github.com/georgestephanis/jetpack-deactivation-helper

It'll add a little `x` to the top right of your activated modules, that will let you deactivate them with a click. We had considered it for inclusion to Jetpack itself, but found people would accidentally click the X when they didn't mean to, and a few other UX issues.

Long story short, it is an issue that we're certainly aware of and working on ways to resolve.

As far as Rocketeer itself, it's doing a couple things that it really shouldn't.

Firstly, when you deactivate the Jetpack plugin by default, it disconnects itself from WordPress.com. This is intentional, as Jetpack is a two-way connection. The JSON API, Site Uptime Monitor, and others need to know whether your Jetpack plugin is active or not -- otherwise things can get troublesome. Rocketeer prevents this from happening ... for no apparent reason.

Secondly, it's actually misleading when it says that Jetpack auto-activates new modules, without asking your permission. This plugin stops that. (linking to Mark's Manual Control plugin) -- Jetpack only auto-activates a modules that provide enhancements without affecting the front-end layout of the site. We're very careful when we make the decision to auto-activate a new module -- both of our latest modules, Single Sign On and Monitor, don't auto-activate.

And even then, they kick on only if we don't detect that you have another plugin installed that duplicates or conflicts with that module's functionality.

So the implication that we're recklessly activating anything that could do bad bad things really is a bit overstating the issue.

All in all, though, I'm glad to see Rocketeer get released. It's a great example of how folks can use all the hooks that we actively seek to include and build add-ons that enhance the experience for users -- which, in the end, is the ultimate goal.