Thanks to Konstantin Kovshenin!

This is a brave service, a bit like Milan's current project at Dev4Press, benchmarking ("Gasp!") plugins ... exposing an 'issue'.

I also try to steer clear of 'suite' plugins, that roll several-to-many different functions into one plugin-package. These make it harder to understand how it works; or to trace a particular behavior; or identify responsibility for data.

I have used some of these. Some are very good; and I like/approve some of the authors.

But invariably, I am using only some of the suite-components, and as I figure things out, I locate simpler, single-function plugins that do the particular thing that I want done. Then I off-load the Swiss Army Knife.

It is a LOT easier to be on top of what our plugins are doing, if each one that we are using (are dependent upon), is a more-modest software creation.

In fact, a good chunk of my collection are plugin-titles that do a task for which there are replacements that are better-made, even better-documented & supported. Still, I try to stick with the ones that are 'basic' enough for me to get my head around.

We can be "locked in" by software that is - to 'us' - a Black Box.