This seems like a weird argument to make: complexity of a spec as some kind of gatekeeper to prevent people from rolling their own implementation? The fact of

This seems like a weird argument to make: complexity of a spec as some kind of gatekeeper to prevent people from rolling their own implementation? The fact of the matter is that these people will probably still not use HTTP/2, but rather stick with their broken HTTP/1.1 implementation, and therefor forever requiring browsers to support this.