A bit nitpicky but: > No HTTPS means worse performance, because HTTP 2.0 requires it HTTP 2.0 actually does not require it, the spec allows for it over unencr

A bit nitpicky but: > No HTTPS means worse performance, because HTTP 2.0 requires it HTTP 2.0 actually does not require it, the spec allows for it over unencrypted connections. All browsers have decided to only enable it over TLS connections though.