this post was submitted on 02 Sep 2026
1192 points (98.7% liked)

Programmer Humor

33104 readers
132 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS
 

you are viewing a single comment's thread
view the rest of the comments
[–] ryannathans@aussie.zone 12 points 2 days ago (4 children)
[–] Mikina@programming.dev 15 points 2 days ago* (last edited 2 days ago) (1 children)

Is it a compression when you need presumably gigabites of a model to reconstruct the data?

It's basically the same as saying I can shatter compressions records by hashing the thing and using a rainbow table to decompress it.

[–] ryannathans@aussie.zone 8 points 2 days ago* (last edited 2 days ago)

A roughly 340MB model at fp16 is all it takes to beat xz and zstd by 2x compression on text

[–] WesternInfidels@feddit.online 3 points 2 days ago (1 children)

They're using domain-specific LLMs to compress narrow-domain data. Their text compression LLM was trained on, and then tested on, legal text and medical text.

There's no reason one couldn't apply the domain-specific-compressor idea to a conventional lossless text compressor, essentially moving much of the dictionary from the compressed file to the program itself. I don't know if anyone's tried that. I'd like to know how that compares.

[–] ryannathans@aussie.zone 3 points 2 days ago

There's a number of compression projects working on this, this is the first that comes to mind

https://bellard.org/nncp/

https://bellard.org/ts_zip/

[–] BlackLaZoR@lemmy.world 2 points 2 days ago

I'd be more interested in lossy compression tho. Few % of image quality loss for multiplying compression ratio is mega useful.