There’s more to it than that. Firstly, at a theoretical level you dealing with the concepts of entropy and information density. A given file has a certain level of information in it. Compressing it is sort of like distilling the file down to its purest form. Once you reached that point, there’s nothing left to “boil away” without losing information.
Secondly, from a more practical point of view, compression algorithms are designed to work nicely with “normal” real world data. For example as a programmer you might notice that your data often contains repeated digits. So say you have this data: “11188885555555”. That’s easy to compress by describing the runs. There are three 1s, four 8s, and seven 5s. So we can compress it to this: “314875”. This is called “Run Length Encoding” and it just compressed our data by more than half!
But look what happens if we try to apply the same compression to our already compressed data. There are no repeated digits, there’s just one 3, then one 1, and so on: “131114181715”. It doubled the size of our data, almost back to the original size.
This is a contrived example but it illustrates the point. If you apply an algorithm to data that it wasn’t designed for, it will perform badly.
it was crucial back in the dial-up internet days or even earlier trying to fit games on a floppy disk. mp3 and mpeg4 came from this quest of course too.
EveryMuffinIsNowEncrypted@lemmy.blahaj.zone 1 day ago
Ohhh you know that makes sense. So, basically, what you’re saying is this?
cam_i_am@lemmy.world 1 day ago
There’s more to it than that. Firstly, at a theoretical level you dealing with the concepts of entropy and information density. A given file has a certain level of information in it. Compressing it is sort of like distilling the file down to its purest form. Once you reached that point, there’s nothing left to “boil away” without losing information.
Secondly, from a more practical point of view, compression algorithms are designed to work nicely with “normal” real world data. For example as a programmer you might notice that your data often contains repeated digits. So say you have this data: “11188885555555”. That’s easy to compress by describing the runs. There are three 1s, four 8s, and seven 5s. So we can compress it to this: “314875”. This is called “Run Length Encoding” and it just compressed our data by more than half!
But look what happens if we try to apply the same compression to our already compressed data. There are no repeated digits, there’s just one 3, then one 1, and so on: “131114181715”. It doubled the size of our data, almost back to the original size.
This is a contrived example but it illustrates the point. If you apply an algorithm to data that it wasn’t designed for, it will perform badly.
EveryMuffinIsNowEncrypted@lemmy.blahaj.zone 9 hours ago
I think this example just confused me honestly. Sorry.
Put another way, though, is it basically like a sock being pushed so far inward that it goes inside-out and gets bigger again?
jamie_oliver@lemmy.world 1 day ago
Man compression is way cooler than I imagined.
Num10ck@lemmy.world 1 day ago
it was crucial back in the dial-up internet days or even earlier trying to fit games on a floppy disk. mp3 and mpeg4 came from this quest of course too.