Are they, though? I mean, is it a feature to make something usable? If you have hard performance constraints and you know what routes you need to suppport, a generic but prohibitively expensive routing strategy can prevent you from using the framework.

> I mean, is it a feature to make something usable?

In your own example, having multiple ways of declaring routing is not required to be considered usable.

So, yes.