http://www.joelonsoftware.com/articles/fog0000000018.html
In reality, SPDY and WebSockets have two very different goals:
* SPDY is a transport optimized for the HTTP request/response service model, down to specific features to compress HTTP-style headers.
* WebSockets is a transport optimized for tunneling bidirectional application-level protocols over an HTTP-style transport.
It's a bit like redesigning a car from scratch just because you need snow chains for certain roads, and upholstery covers for certain passengers.
The two descriptions you make below describe much more essentially than superficially or "astronautically", the same kind of thing, optimized for slightly different use cases (not even THAT different).
It would have yielded the same thing as W3C's decade long stagnation during the development of XHTML: everyone gets bored and they set up WhatWG instead.
Would that have yielded something better? I would argue that it would have yielded nothing.
Though nonetheless I am a bit confused by your comparison of the two. WebSockets are not "another way of doing HTTP". SPDY is. They are separate solutions for different problems.