lemming_7765

joined 2 years ago
[–] [email protected] 4 points 2 years ago (2 children)

Maybe edit the title so that people not reading the comments (and the article) are aware? πŸ€”

[–] [email protected] 1 points 2 years ago

I guess it all depends on what you understand by compression. If you are OK with lossy compression then it can be a valid path to investigate. If, on the other hand, you need non destructive compression I doubt text can be very efficient given how much redundacy our languages have.

In the end, a compression algorithm is a map function from a huge space to a much smaller one that assumes that, because not all values in the original map are statistically equivalent (in the sense that some of them are not valid or not interesting at all) the mapping will work most of the time and will reduce the data you need to store the values.

For a extremely lossy algorithm I think a text description of the image would do OK, but it would mean that you don't care about the image detail at all. Meaning that if you describe an image like "a man in a horse in a sunny day", that's all you care about and you are OK with getting different images when they are rendered.

To sum up: compression is already mathematically defined no matter what method you use, and has its limits. You could argue that maybe we can find a new mathematic definition of another thing we may call compression, but I really doubt it given how well established is the information theory. πŸ€·β€β™‚οΈ

[–] [email protected] 2 points 2 years ago (2 children)

Did you send the money? It would be nice to have him record new albums... πŸ’ͺ

[–] [email protected] 2 points 2 years ago

Makes sense. I've also given a try to the flags I mentioned in rustfmt and they are apparently just for the nightly build, which makes me think they are working on it, which is good news (at least for me).

Sometimes having too much freedom when it comes to organizing code can be worse, I guess. But in general I prefer it to, for example, C, which was so picky with the placements of things.

Thanks for the feedback πŸ‘

[–] [email protected] 1 points 2 years ago (2 children)

That's more or less what I do. However I usually struggle with enum, traits, functions and structs inside the same group. So, for example, if I'm in the public group:

  1. do I mix them all and sort alphabetically or hierarchically (like the post https://lemmy.ml/comment/414806 suggests)?
  2. do I put enums, traits and functions first since they are usually prerequisites for the following types? Meaning that an enum will probably be used in a struct or trait, so we may want to present it before to the reader.
  3. any other sorting....

πŸ€”

[–] [email protected] 1 points 2 years ago

So, hierarchichal top down, I guess. With main types before subordinate ones. Right?

 

I would like to know if there are any proposals for internal file organization, like what to put from top to bottom...

Example: start with pub use declarations, then use, the mod, enums, traits, etc.

I've seen rustfmt has some options like reorder_imports that may impose some partial structure, but I would like a more comprehensive guide/spec...

If there's nothing like that. Can we maybe discuss something that makes sense? πŸ€”

[–] [email protected] 3 points 2 years ago (1 children)

Nah, we just need to create another humongous economic bubble and things will go back to normal... 🧌

[–] [email protected] 1 points 2 years ago

Maybe that's a sign that it is not mature enough πŸ˜‚

[–] [email protected] 1 points 2 years ago

Intriguing. Reminded me of Nick Bostrom's essays on ethical implications regarding simulations and AI...

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago) (1 children)

IINM, you shouldn't that because it would defeat the purpose of this browser, which is to maintain the same fingerprint for everybody.

view more: next β€Ί