Compression-dictionary-transport Alternatives

compression-dictionary-transport reviews and mentions

• Compression efficiency with shared dictionaries in Chrome
  3 projects | news.ycombinator.com | 6 Mar 2024

  > Dictionary entries (or at least the metadata) should be cleared any time cookies are cleared.

  So it seems it should not get you anything you cannot already do with cookies.

  https://github.com/WICG/compression-dictionary-transport?tab...

• Chrome feature: Compression dictionary transport with Shared Brotli
  2 projects | news.ycombinator.com | 22 Sep 2023

  Talked about here:

  https://github.com/WICG/compression-dictionary-transport

• Compression Dictionary Transport
  1 project | news.ycombinator.com | 9 Aug 2023
• Improving compression with a preset DEFLATE dictionary (2015)
  1 project | news.ycombinator.com | 24 Jul 2023

  There's a spec up for custom dictionary support across the web. https://github.com/WICG/compression-dictionary-transport

  This was one of the major blockers that iirc Mozilla threw in the way of zstd compression support: they said zstd with a standardly accepted dictionary would be too particular & wanted more. With this spec maybe Moz will accept zstd as a web compression standard.

• JavaScript import maps are now supported cross-browser
  14 projects | news.ycombinator.com | 3 May 2023

  Here here. Today, bundlers may get you to first page load faster. But if a user comes back and you've shipped two small fixes, all those extra wins you get from compressing a bunch files at once fly out the window & you're deep in the red. If you have users that return to your site, and your site is actively developed, bundling is probably a bad tradeoff.

  We see similar fixedness in the field all over the place: people freaking love small Docker image sizes & will spend forever making it smaller. But my gosh the number of engineers I've seen fixate on total download size for an image, & ignore everything else, is vast. Same story, but server side: my interest is in the download size for what v1.0.1 of the Docker container looks like once we already have v1.0.0 already shipped. Once we start to consider what the ongoing experience is, rather than just the first time easy-to-judge metric, the pictures all look very different.

  Then there's the other thing. The performance reasons for bundling are being eaten away. Preload & Early Hints are both here today & both offer really good tools to greatly streamline asset loading & claw back a lot of turf, and work hand-in-glove with import-maps. The remaining thing everyone points out is that a large bundle compresses better (but again at the cost of making incremental updates bad). The spec is in progress, but compression-dictionary-transport could potentially obliterate that advantage, either make it a non-factor, or perhaps even a disadvantage for large bundles (as one could use a set of dictionaries & go discover which of your handful of dictionaries best compress the code). These dictionaries would again be first-load hit, but could then be used again and again by users, to great effect again for incremental changes. https://github.com/WICG/compression-dictionary-transport

  Bundles are such an ugly stain on the web, such an awful hack that betrays the web's better resourceful nature. Thankfully we're finally making real strides against this opaque awful blob we've foisted upon this world. And we can start to undo not just the ugliness, but the terrible performance pains we've created by bundling so much togther.

• A note from our sponsor - InfluxDB
  www.influxdata.com | 26 Apr 2024

  Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →