If you don't want to deal with certificates just keep using HTTP 1.1. If you want the speed and security improvements of 2.0, certificates will get cheaper and

If you don't want to deal with certificates just keep using HTTP 1.1. If you want the speed and security improvements of 2.0, certificates will get cheaper and easier to obtain. Most of the certificate authorities' costs are one-time (validating identity). Issuing subsequent certificates costs them nothing. Pricing will adjust accordingly with increased demand (and in some cases already has). A fixed dictionary for header compression is a lot better than no compression dictionary. Negotiation would be added complexity/latency. Sure you could argue either way but it doesn't seem like a big deal. Google has done a great job on SPDY. It's proven at scale and performs really well. Making it a standard is a great move.