Auzy•

The problem for a lot of us is that nginx doesn't support it yet

12
coladict•

I thought the problem was that it didn't deserve to be versioned as 2.0 for changing so little, so everyone was disappointed and turned away.

6
Auzy•

It still does change something though. It would be interesting to see though if quic is adopted more quickly

3
vertice•

i've not seen quic mentioned outside of docker / coreos / go circles. has the been any adoption outside that?

3
wtallis•

QUIC can't and won't be adopted widely. It's an experimental testbed, not something that is appropriate for wide deployment. In at least one way (ECN support) it's a big step backwards from existing TCP-based protocols.

QUIC is basically about trying whatever is possible without modifying the operating system, so that the ideas can be more fully developed and concretely specified before trying to get Microsoft to change their TCP stack. But it's targeting lower-level changes than SPDY did, so it will ultimately require OS changes in order to be a complete replacement for the protocols it's trying to improve upon.

3
[deleted]•

[deleted]

1
tootie•

Big guys like Google, Facebook, Twitter and CDNs like akamai or CloudFlare are already rolling out support on their proprietary platforms. That will account for a ton of web traffic with or without broader adoption by the zillions of smaller sites. Even if nginx and Apache supported it now, it would take years for everyone to upgrade.

3
gearvOsh•

This is exactly what I'm waiting for.

1
corppneq•

Actual Support by Country is a pretty useless chart. These are absolute numbers. How many of the Alexa top 1 million sites are from the States?

6
MsEtheldreda•

It should be percentages really.

2
issafram•

Windows Server 2016 and IIS 10 will show more use from a windows standpoint.

4
vertice•

i was really not expecting SPDY to be sidelined the way it was. I mean, nginx only got support for that like "yesterday". I was even building open source projects around SPDY.

Now we need to wait for the http2 ecosystem to stabilize a bit more.

I wonder if there are any decent node implementations yet. I know the Go one is undercooked.

3
immibis•

You weren't expecting Google to drop support for one of its experimental new technologies?

3
vertice•

I did, but I expected the transition to go a bit more smoothly than it has. Certainly not 'this is dead, because we committed that'.

I also hoped that http2 would have more mature implementations out before we adopted it wholesale (not that i'm saying spdy was better in any way).

3
kurin•

How was it sidelined?

3
vertice•
2
kurin•

Yeah, SPDY was the basis for HTTP/2. Several members of the working group were involved in SPDY.

7
dvlsg•

I think the last time I looked at this one it was functional. Not sure about decent though.

2