4 ms·

That’s not been true since Site Isolation IIRC e: Not sure it’s Site Isolation specifically, but it’s definitely still not true anymore: https://news.ycombinat

That’s not been true since Site Isolation IIRC e: Not sure it’s Site Isolation specifically, but it’s definitely still not true anymore: https://news.ycombinator.com/item?id=24745748 https://news.ycombinator.com/item?id=24745748 e2: listen to the commenter below, its Cache Partitioning: https://developer.chrome.com/blog/http-cache-partitioning https://developer.chrome.com/blog/http-cache-partitioning

andrewmcwatters 2y ago
If that's true, this is a wild microcosm example of how the web breaks in ways we don't expect.
- collinmanderson 2y ago
  > this is a wild microcosm example of how the web breaks in ways we don't expect. I think the performance characteristics of the web are subject to change over time, especially to allow increased security and privacy. https is another example of increased security+privacy at the cost of being slightly slower than non-https connections because of an extra round trip or two to create the connection. The lesson I take from it is: don't use complicated optimization techniques that might get out of date over time. Keep it simple instead of chasing every last bit of theoretical performance. For example, there used to be a good practice of using "Domain Sharding" to allow browsers to download more files in parallel, but was made obsolete with HTTP/2, and domain sharding now has a net negative effect, especially with https. https://developer.mozilla.org/en-US/docs/Glossary/Domain_sharding https://developer.mozilla.org/en-US/docs/Glossary/Domain_sha... Now they're realizing that HTTP/2's multiplexing of a single TCP connection can have negative effects on wireless connections, so they're working on HTTP/3 to solve that. Also don't use polyfills. If your supported browsers don't support the feature then don't use the feature, or implement the fallback yourself. Use the features that are actually available to you.
simonw 2y ago
Right - and site isolation is about five years old at this point. The idea that CDNs can share caches across different sites is quite out of date.
can16358p 2y ago
Didn't know that. Then why are we (I mean, many web devs) still using it? Just an old convention, simplicity, or saving bandwidth?

andrewmcwatters 2y ago

If that's true, this is a wild microcosm example of how the web breaks in ways we don't expect.

collinmanderson 2y ago
> this is a wild microcosm example of how the web breaks in ways we don't expect. I think the performance characteristics of the web are subject to change over time, especially to allow increased security and privacy. https is another example of increased security+privacy at the cost of being slightly slower than non-https connections because of an extra round trip or two to create the connection. The lesson I take from it is: don't use complicated optimization techniques that might get out of date over time. Keep it simple instead of chasing every last bit of theoretical performance. For example, there used to be a good practice of using "Domain Sharding" to allow browsers to download more files in parallel, but was made obsolete with HTTP/2, and domain sharding now has a net negative effect, especially with https. https://developer.mozilla.org/en-US/docs/Glossary/Domain_sharding https://developer.mozilla.org/en-US/docs/Glossary/Domain_sha... Now they're realizing that HTTP/2's multiplexing of a single TCP connection can have negative effects on wireless connections, so they're working on HTTP/3 to solve that. Also don't use polyfills. If your supported browsers don't support the feature then don't use the feature, or implement the fallback yourself. Use the features that are actually available to you.

simonw 2y ago

Right - and site isolation is about five years old at this point. The idea that CDNs can share caches across different sites is quite out of date.

can16358p 2y ago

Didn't know that. Then why are we (I mean, many web devs) still using it? Just an old convention, simplicity, or saving bandwidth?