I agree that adding BruteProtect to JetPack is the right answer for "the vast, vast majority of WordPresses in the world", and I understand this decision within that context.

However saying "some advanced users may not like that" will I expect prove to more than a little understated. There is clearly at this stage significant resistance from many WordPress Developers to being effectively forced to use Jetpack to gain access to BruteProtect.

Some of that resistance might be overcome by the JetPack team fleshing out Matt's comment that advanced users "can have plugins or filters to alter how JP works". It makes sense to listen to the concerns expressed here and develop hopefully relatively simple ways to overcome them.

Nevertheless I expect that many advanced users will remain resistent to using JetPack and look for alternatives to BruteProtect.