3 ms·

I think giving up on the web is doubly wrong, because these days, the web is constantly changing. Just this week we've seen how QUIC/HTTP3 is a big thing, and i

I think giving up on the web is doubly wrong, because these days, the web is constantly changing. Just this week we've seen how QUIC/HTTP3 is a big thing, and it's a leap from HTTP2, and a huge leap from 1.1. We've seen small revolutions all over the place. Yeah, it's not clear which ones will "stick" but I think there's still time for meaningful change that doesn't require boiling the ocean.

eznzt 6y ago
Isn't QUIC/HTTP3 a protocol that improves the performance of pipelining which is something that very bloated webpages benefit from? Isn't that something we should move away from?
- Dylan16807 6y ago
  Sometimes you want to load a bunch of thumbnails. Pipelining is pretty good. Though you can pipeline just fine on HTTP/1.1 if people would actually enable it.
- rektide 6y ago
  Pipelining is something that helps everyone other than the gigantic new breed of "single page web apps" that are actually just single gigantic JS files. We should definitely definitely definitely be trying to help pipelining. Unless you send only one resource, pipelining is probably a huge win. And it definitely, from the server side, makes things way easier. As you can get a bunch of requests & start satisfying them in whatever order works for you. This isn't like HTTP 1.1 Pipelining, which was in order: now connected systems can out of order send whatever data they have, without having to buffer it & wait for the first asked for data to clear the pipe. This is massively massively helpful tech we are creating. Attaching it to "very bloated webpages", & implying this is something "we should move away from" is a high level of shade that is not at all in any way deserved nor fair nor accurate.
- neurobashing 6y ago
  I was arguing less for a specific tool, technology, or whatever, and more that the web as platform is constantly in flux and so "throwing it away" makes no sense. You don't stop using the Interstate system bc a stretch of road is bad.

eznzt 6y ago

Isn't QUIC/HTTP3 a protocol that improves the performance of pipelining which is something that very bloated webpages benefit from? Isn't that something we should move away from?

Dylan16807 6y ago
Sometimes you want to load a bunch of thumbnails. Pipelining is pretty good. Though you can pipeline just fine on HTTP/1.1 if people would actually enable it.
rektide 6y ago
Pipelining is something that helps everyone other than the gigantic new breed of "single page web apps" that are actually just single gigantic JS files. We should definitely definitely definitely be trying to help pipelining. Unless you send only one resource, pipelining is probably a huge win. And it definitely, from the server side, makes things way easier. As you can get a bunch of requests & start satisfying them in whatever order works for you. This isn't like HTTP 1.1 Pipelining, which was in order: now connected systems can out of order send whatever data they have, without having to buffer it & wait for the first asked for data to clear the pipe. This is massively massively helpful tech we are creating. Attaching it to "very bloated webpages", & implying this is something "we should move away from" is a high level of shade that is not at all in any way deserved nor fair nor accurate.
neurobashing 6y ago
I was arguing less for a specific tool, technology, or whatever, and more that the web as platform is constantly in flux and so "throwing it away" makes no sense. You don't stop using the Interstate system bc a stretch of road is bad.