You get the exact same quality at around ~25% smaller than other image formats. Unfortunate that it’s not supported by everything, but yeah it’s a better image format practically in that sense.
On the web this saves money when storing at a large scale, and it can have a significant impact on page speed when loading websites on slower connections.
My problem is the way it’s packaged as a link to a website that hosts the jpeg image. Saving, modifying, and using the image file becomes impossible in some workflows. Imagine a future where you get fined for stealing memes. I bet they could make the image file size even smaller without all of that bullshit added in, until then I’m just using an extension to convert to png (which results in loss btw).
You are saying that you use an extension to convert from WebP to PNG, right? PNG is a lossless file format. It’s compressed, but losslessly. Like zip is also lossless compression. You can remove information to make it more compressible and then it’s a lossy process, but that’s not because of PNG, but because of the specific workflow.
I’d rather see the savings in the army of Javascript I apparently need today for the ‘modern’ web experience. Image files have gotten lots of love, but hey, here’s a shitty 27 year old language designed for validating form input!
There are more places where bandwidth is a bottleneck now than 10 years ago.
NIC speeds have gone from 100Gbps to 800Gbps in the last few years while PCIe and DRAM speeds have nowhere increased that much. No way are you going to push all that data through to the CPU on time. Bandwidth is the bottleneck these days and will continue to be a huge issue for the foreseeable future.
You get the exact same quality at around ~25% smaller than other image formats. Unfortunate that it’s not supported by everything, but yeah it’s a better image format practically in that sense.
On the web this saves money when storing at a large scale, and it can have a significant impact on page speed when loading websites on slower connections.
My problem is the way it’s packaged as a link to a website that hosts the jpeg image. Saving, modifying, and using the image file becomes impossible in some workflows. Imagine a future where you get fined for stealing memes. I bet they could make the image file size even smaller without all of that bullshit added in, until then I’m just using an extension to convert to png (which results in loss btw).
deleted by creator
Converting FROM a format to a DIFFERENT FORMAT can cause loss. In this case from one compressed type to another.
deleted by creator
Or the output is a comic strip about a miscarriage.
:.|:;This is the most compressed meme
deleted by creator
You are saying that you use an extension to convert from WebP to PNG, right? PNG is a lossless file format. It’s compressed, but losslessly. Like zip is also lossless compression. You can remove information to make it more compressible and then it’s a lossy process, but that’s not because of PNG, but because of the specific workflow.
deleted by creator
Not true.
It’s already supported in many more places than it was a couple years ago. It just takes time.
I’d rather see the savings in the army of Javascript I apparently need today for the ‘modern’ web experience. Image files have gotten lots of love, but hey, here’s a shitty 27 year old language designed for validating form input!
Save a lot more debloating your code. Storage is cheap. Processing power is not.
There are still places where bandwidth is a bottleneck, even on internal network is essential to optimize for bandwidth
There are more places where bandwidth is a bottleneck now than 10 years ago.
NIC speeds have gone from 100Gbps to 800Gbps in the last few years while PCIe and DRAM speeds have nowhere increased that much. No way are you going to push all that data through to the CPU on time. Bandwidth is the bottleneck these days and will continue to be a huge issue for the foreseeable future.