Hacker News new | ask | show | jobs
by josteink 4144 days ago
This is what happens when you let Google (or other big corporations) write internet-standards.

If it isn't community-driven, you can't expect it to be implemented in the places the big corp doesn't care for.

So in this case, Apache one of the major drivers for propelling the WWW may end up not supporting a "crucial" WWW-related standard, because the community was never invited.

If anyone still has any doubts why letting Google control internet-standards is bad, this is currently my best example.

Technically speaking, the internet is the result of what we come up with, when we all work together. Not working together will quickly end up as not working at all.
1 comments
netik 4144 days ago
I think the reality here is, this is what happens when you let companies fight over a standard in private.

What I saw on the HTTP/2 mailing lists was "We have a new standard." "It demands SSL, but we don't want that." Then, SPDY is everywhere, let's use that.

Shortly after it was "Omg, we can't call it spdy, because then Microsoft's interests will be left behind and Google will have won. Let's abandon the mandatory SSL requirement and rename SPDY to HTTP2..."

I feel like we've all lost here.

We implemented SPDY at Twitter - the savings were fantastic and the browser performance, amazing. Google and FB did the same. It's nearly like, 800M users said it was great, can we move on now?

link