431
jprule
(lemmy.blahaj.zone)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Sep 2025
431 points (98.2% liked)
196
18411 readers
343 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts are not allowed
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
For f*&% sake, I'm using JPEG XL on my website for some high res images that are amazingly well compressed using it, and especially to reduce the repository size on Codeberg. Only now discovered that only my niche main browser, Zen, renders them. What a stupid decision; their compression of high quality images is superior. Perfect to use alongside AVIF which does better in low quality images and illustrations and the like, or PNG which is best at preserving images containing text such as screenshots.
Safari renders them.
Firefox forks usually render them because Firefox supports it but Mozilla takes it out of packaged builds.
I had the luxury of seeing incredibly smart engineers speak about their new innovations for web development.
I then got to watch them get hired by Google and paid extremely well to release those innovations, with the support of a bunch of other brilliant people, often under a open-source label.
I then get to see people go, "Google Bad!" About those features, and because it was paid for by Google, they don't even want to touch it.
WebP and AVIF are good at what they do, it's just that Google insists on them being the only modern formats people should ever use, despite different formats being better in specific contexts.
I don't think people would be as upset if Google gave people the choice to use other formats. The standards aren't the problem, the monopoly is.
Google is an enormous beast. It doesn't care about you, or me, or the good of anyone. Sometimes its goals happen to align with a common good for awhile - and so good stuff can come from that. But often their goal do not, and they cause harm while crushing any possible alternative path. And as time goes on, less and less of what google does is for the common good.
For that reason, I think it is unwise to support google. Supporting them further entrenches their power, preventing others from contributing.
The smart engineers you spoke of would still be smart engineers with or without google. Google didn't create them. They can still contribute with or without Google. But Google did direct their efforts to suit Google's own needs. - Sometimes that's also good for other people, but often it is not.