Not the good kind of innovation. Some nerds won an argument about HTTP semantics. Rails used to understand the importance of convention. This just seems silly and meaningless, change just for change.
Maybe it is, maybe it's not, but I don't think moving from technically incorrect to technically correct is change for change's sake. There's benefits to doing things by spec even if they are not immediately obvious.
I think what you're saying though is that the downsides are. You may be right on that, but I'm going to withhold judgement until I really figure out what this means.
