Now, if the name was something like HTTP/1.8-alpha it might be a different thing. At least then it wouldn't carry the label of the "next big thing for everyone". It's sad, but names (and branding) do matter. Forcing a known-broken implementation upon the world is not exactly good engineering.
Google in-houses everything so a single fast multiplexed connection to a single server makes sense. Every other website has external content, ads, like buttons, etc. and you end up having to spin up 30-40 independent SPDY connections, eliminating all benefit.
And I'm very afraid of the following phrase:
"we found out that there are numerous hard problems that SPDY doesn't even get close to solving, and that we will need to make some simplifications in the evolved HTTP concept if we ever want to solve them."
This usually means "ending up with a protocol that has a lot of corner cases and a lot of backward-compatible crap or maybe some half-baked stuff that was left because of some feature that nobody uses"
I am very skeptic of protocols/standards that are born from a committee (take a look at telephony protocols/standards if you doubt me)
It was revolutionary at the time but people have moved on and found many improvements to the original and also outright mistakes.
(As the author seems to have acknowledged when releasing a new improved iteration of his book.)
That hardly means that what it has to teach isn't still valid. Admittedly, I've only read a few chapters in it, but the central point that throwing more man power at a late project only serves to make it later, is at least as relevant today as when the book was first published.
> It was revolutionary at the time but people have moved on and found many improvements to the original and also outright mistakes.
Could you be more specific?
> (As the author seems to have acknowledged when releasing a new improved iteration of his book.)
So, do your points above refer only to the first edition of the book then?
This is only part of the book. And as per this thread there's a lot more to the book . IE we are specifically talking about it's comments on prototyping which the original OP mentioned in their email.
It's been years since I read it, but I'll toss in this review with their points -http://www.goodreads.com/review/show/882155551?book_show_act...
To me, to believe one persons opinionated book from 40 years ago as relevant today is just plain wrong. Even things like the way science was done back then is in questionable today.
Systems they developed will be improved on, technology and societal change will make specifics no longer totally accurate and one person won't get an entire book right.
I would also accept an interpretation where that's an indictment on the field.
Few books in our industry have been more prescient.