News for hackers. Stuff that matters.
Re:Mozilla rejects Google's WebP image format by kevingadd on Tuesday May 24, 2011 @08:00PM (#2582241)
I've yet to see a compelling argument for why I should want a browser with WebP support. Unless images start out lossless, and then are encoded into WebP directly, all I'll ever get out of WebP is smaller images that have more encoder artifacts - and I don't want that. I've got plenty of bandwidth; I'd rather download images in their original JPEG or PNG formats, especially if that means I can then open them up in any image editor or viewer on my computer, instead of having to install some special (and likely buggy) new WebP viewer/converter.

I think if WebP offered useful features JPEG doesn't, like alpha channel support or support for higher bit depths or useful new metadata, that'd at least justify it, and people would be creating new demos that showed off the technology. We saw this with the uptake of support for PNG after people started showing how PNG's support for alpha transparency made it possible to do interesting things that you couldn't with JPEG/GIF. WebP has no such compelling feature.

Re:Mozilla rejects Google's WebP image format by ansy on Tuesday May 24, 2011 @09:59PM (#2582571)
We don't have plenty of bandwidth with mobile applications. It's quite common for even basic sites to slow to a crawl on 3G. Even with LTE just around the corner, richer multimedia at higher resolutions will partially offset those gains.

Note that according to Nielsen's Law bandwidth growth rate, while sill exponential, is slower than Moore's Law (transistor count) and Kryder's Law (disk space), so we will be increasingly bandwidth limited as time continues [1]. For an example just look at SSD hard drives. To overcome bandwidth limitations the best SSDs now have whole ARM based computers in them to compress data on the fly, reorder operations on the fly, and run its own garbage collection programs just to save from going over the already very fast SATA bus which the latest drives fully saturate.

[1] http://en.wikipedia.org/wiki/Nielsen%27s_Law#Contributions

Re:Mozilla rejects Google's WebP image format by ericd on Wednesday May 25, 2011 @12:52AM (#2582911)
SATA is saturated because the increase in performance between platter disks and SSDs is a big discontinuity in what had been a relatively slow but steadily rising curve in the max sequential speed of a disk. Right now SATA is playing catchup, and has had two fairly major iterations in a much shorter cycle than what used to be the case. SATA 6gbps isn't saturated by even the Vertex 3.

Mobile bandwidth is a problem for completely different reasons - I wouldn't equate them.

Re:Mozilla rejects Google's WebP image format by tintin on Wednesday May 25, 2011 @03:45AM (#2583255)
"We don't have plenty of bandwidth with mobile applications."

Because mobile devices have screens with 300ppi it's not a bad idea to use GIF or PNG files with less than 64 colors (adaptive). When you use dither (patern) the results are quite good given the filesize.