> Stateless? What about that hack known as cookies? Aren't they useful? How about HTML5? I dislike both. > And what happened to the calls for SSL everywhere?

> Stateless? What about that hack known as cookies? Aren't they useful? How about HTML5? I dislike both. > And what happened to the calls for SSL everywhere? It should be, it's just not HTTPs job to provide that > I'm shocked that your only objection ends up being the protocol name. I get upset whenever the next version of something is entirely different in philosophy and design than its predecessors. Use spdy:// or something. You can use the HTTP upgrade mechanism, or something like STS to tell a browser that it accepts the new protocol.