Decisions are never easy.
Even if it’s an entirely trivial matter, it’s still forcing you to do something.
And goshdarnit, I’m lazy.
I also prefer front-loading effort when possible. Ounce of prevention, pound of cure, stitch in time saving nine, and all that.
And I respect other people’s time as much as I value my own. So when I build something, I try to avoid decision points whenever possible. This results in the loss of options occasionally, but I believe a smoother user flow.
Now, occasionally power-users will want to modify functionality. Adding a decision point for all users for the sake of the minority is silly, especially when power-users can leverage other methods — filters, actions, functionality plugins that extend the first plugin — to accomplish their goals.
To each according to their needs. Typical users need a simple, smooth, classy interface. Power users need to get under the hood. Why try to make something that doesn’t work well for either by trying to serve both?
The best middle ground I’ve been able to come up with is offering a secondary ‘under the hood’ plugin that exposes a lot of filters as options. Keep it canonical and clean, but present all the options.
Ideal? Not really. Workable? Probably.