this post was submitted on 29 Jun 2024
705 points (91.4% liked)

memes

10393 readers
1901 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/AdsNo advertisements or spam. This is an instance rule and the only way to live.

Sister communities

founded 1 year ago
MODERATORS
Tenthrow@lemmy.world
The_Picard_Maneuver@lemmy.world
The_Picard_Maneuver@startrek.website
705
goddamnit (fedia.io)
submitted 4 months ago by downpunxx@fedia.io to c/memes@lemmy.world
141 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] Emerald@lemmy.world 2 points 4 months ago (2 children)

My only concern with jpeg xl is... how do you know if the encoded file is losslessly compressed or not?

with jpg and png, one is lossless, one is not. But if all the files have a jxl extension, you can't know unless the encoder adds metadata for it, right?

[–] Persi@lemm.ee 2 points 4 months ago

I felt the same way about webp when it came out.

In practice it doesn't really matter:

  • if you're encoding the file you know how you're doing it.
  • if you're receiving the file, you get the pixels you get no matter how it was encoded.
  • if you're sending the image through some third party service, they're going to reencode and mangle it anyway so there's no point in worrying.

Also, it turned out that even if it's quite good, lossless webp is rarely seen in the wild because svg is more convenient.

[–] brucethemoose@lemmy.world 1 points 4 months ago

I mean the application could tell by looking at how its encoded, right?

Though I acknowledge how problematic "trusting" the app to do that is.