Nor does it imply quality in and of itself.

>>"Responsive" is pretty factual - something either is or it isn't responsive.

"Car" is pretty factual. There's all kinds of cars...

Sure, but if you want to drive on the road, it's still at least a bit helpful to know that the framework is not, in fact, a boat. (I wonder if someone could give a Devil's Advocate position on the advantages of a non-responsive framework...)

Advantages of a non-responsive framework: Less complexity. This leads to more speed and reliability in terms of development, deployment, and maintenance.

If I was building something that saw no significant advantages from being responsive (e.g. an ATM GUI) I'd definitely skip it.