And perhaps the whole Agile packaging was too sloppy. Like, lets package up some nice-to-haves for C++ and we shall call it Java. Once you unwrap it, the thing inside doesn't stand on its own. Don't mean to bash Java but I think it suffers the same problem as the article described.
Though, I like what you said, focus on merits. Don't just talk about it. Experience it. Live it. Once we have done that, then what we call it is just secondary. It is the "quality without a name" ;-)