you’re comparing a format released almost 15 years ago with one released ~2 years ago. does h264 suck just because h265 exists? it depends on support and what you’re trying to accomplish.
Here, re-encode all your images for a minuscule amount of kilobytes saved into a format that can’t be read in older computers when JPG and PNG work just fine.
Nobody is saying you need to use webp locally. But when you’re talking about the entire fucking world on the internet sharing images, even minuscule savings scales to something appreciative.
Another aspect to consider is, not everyone is privileged with unmetered internet access. Shoving bloated media into peoples’ faces is actively costing real people real money. If you’re operating even a modestly popular site, I feel like you have a moral obligation to ensure it’s as inexpensive to browse as possible.
“entire fucking world on the internet” is streaming movies and endless series while videoCalling to babble nothings and you’re defending webp over png because it saves a dozen kbps?
i chose to be on data cap. it’s not the difference between image formats that will get me overlimit
people on data caps don’t matter is asinine.
where did i imply that?
my response was to “But when you’re talking about the entire fucking world on the internet sharing images, even minuscule savings scales to something appreciative.”
Any amount of bandwidth/data cap saved across 8 billion people is appreciable. Full stop, that’s all I’m saying. If you don’t wanna acknowledge that point there’s really nothing else for us to say here.
There’s no real savings because the web is bloated with ads and JavaScript frameworks. If you really want to save some kilobytes, learn to write lean web code.
Oh, when your done converting all your images to webp, be sure to do it again with JpegXL. After that I’m sure another new and shiny standard will be released.
I’m not even trying to change your mind on webp I don’t give a shit. But ingesting images on your platform and serving them efficiently is part of writing lean code and you’re just arguing for arguments sake.
why?
Because it’s not JXL
you’re comparing a format released almost 15 years ago with one released ~2 years ago. does h264 suck just because h265 exists? it depends on support and what you’re trying to accomplish.
Here, re-encode all your images for a minuscule amount of kilobytes saved into a format that can’t be read in older computers when JPG and PNG work just fine.
Nobody is saying you need to use webp locally. But when you’re talking about the entire fucking world on the internet sharing images, even minuscule savings scales to something appreciative.
Another aspect to consider is, not everyone is privileged with unmetered internet access. Shoving bloated media into peoples’ faces is actively costing real people real money. If you’re operating even a modestly popular site, I feel like you have a moral obligation to ensure it’s as inexpensive to browse as possible.
“entire fucking world on the internet” is streaming movies and endless series while videoCalling to babble nothings and you’re defending webp over png because it saves a dozen kbps?
I’m not defending webp over png. All of my sites serve both depending on what the browser indicates it supports. It’s zero effort.
Implying that because people with unmetered internet are live-streaming, people on data caps don’t matter is asinine.
i chose to be on data cap. it’s not the difference between image formats that will get me overlimit
where did i imply that?
my response was to “But when you’re talking about the entire fucking world on the internet sharing images, even minuscule savings scales to something appreciative.”
Any amount of bandwidth/data cap saved across 8 billion people is appreciable. Full stop, that’s all I’m saying. If you don’t wanna acknowledge that point there’s really nothing else for us to say here.
this is a 9kb image from a screenshot of different sizes of Veritasium’s last video 👇
how many webp images can you serve instead of even the 360p version?
what you’re saying is of no consequence is what i’m saying. good day to you too
There’s no real savings because the web is bloated with ads and JavaScript frameworks. If you really want to save some kilobytes, learn to write lean web code.
Oh, when your done converting all your images to webp, be sure to do it again with JpegXL. After that I’m sure another new and shiny standard will be released.
I’m not even trying to change your mind on webp I don’t give a shit. But ingesting images on your platform and serving them efficiently is part of writing lean code and you’re just arguing for arguments sake.
How old before the computers aren’t able to read the format?
My very new Mac can’t read them because the OS doesn’t support in natively and I won’t use non-standard formats.