News for hackers. Stuff that matters.

A comment on Compression efficiency with shared dictionaries in Chrome. Parent comment

Re:Compression efficiency with shared dictionaries in Chrome by hinkley on Wednesday March 06, 2024 @02:49PM (#39620457)
I think I’d feel better with a fixed set of dictionaries based on a corpus that gets updated every year to match new patterns of traffic and specifications. Even if it’s less efficient.
[ Parent | on HN ]
Re:Compression efficiency with shared dictionaries in Chrome by pyrolistical on Wednesday March 06, 2024 @04:01PM (#39621392)
Ya. Where is accept-encoding: zstandard-d-es2024

Where it encodes js files with a known dictionary that is ideal for es2024

[ Parent | on HN ]
Re:Compression efficiency with shared dictionaries in Chrome by hinkley on Wednesday March 06, 2024 @05:01PM (#39622230)
And here’s one tuned for react, and one for svelte…
[ Parent | on HN ]
Re:Compression efficiency with shared dictionaries in Chrome by pyrolistical on Wednesday March 06, 2024 @07:03PM (#39623428)
That wouldn’t make sense as it would be the user agent (aka your browser) that implements these shared dictionaries and they wouldn’t be able to add non-standard shared dictionaries for libs like react.

If they could do that then they might as well preload the cache with all common libs like react from well known cdn urls.

[ Parent | on HN ]
Re:Compression efficiency with shared dictionaries in Chrome by hinkley on Wednesday March 06, 2024 @11:58PM (#39625189)
Committee decided set of dictionaries.

I never cared for react, but I know beyond a doubt that someone influential will ask for a dictionary tuned for it.

[ Parent | on HN ]