Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Google Graphics Mozilla Technology

Mozilla Rejects WebP Image Format, Google Adds It 262

icebraining writes with a link to Ars Technica's look at the recent rejection of WebP by Mozilla Developer Joe Drew."Building mainstream support for a new media format is challenging, especially when the advantages are ambiguous. WebM was attractive to some browser vendors because its royalty-free license arguably solved a real-world problem. According to critics, the advantages of WebP are illusory and don't offer sufficient advantages over JPEG to justify adoption of the new format. (...) 'As the WebP image format exists currently, I won't accept a patch for it. If and when that changes, I'll happily re-evaluate my decision!' wrote Mozilla developer Joe Drew in a Bugzilla comment.'" However, as the article explains, Google sees enough value in WebP to add it as a supported image format for Picasa.
This discussion has been archived. No new comments can be posted.

Mozilla Rejects WebP Image Format, Google Adds It

Comments Filter:
  • Re:Why NOT? (Score:5, Informative)

    by cpu6502 ( 1960974 ) on Tuesday May 24, 2011 @08:49PM (#36234740)

    Quote: "Adopting a new image format in Web browsers is a big decision. Once a format becomes a part of the Web, it will have to be supported in perpetuityâ"adding overhead to the browserâ"even if it largely fizzles and only gains a small niche following."

    It's akin to if Web browsers were required to support failed formats like ANIM or HAM or IFF. In other words adding support for WebM wastes space in the program (and computer memory).

    And I'm probably going to get modded -1 for comparing WebM to "failed formats" like HAM, but I think it's pretty obvious that WebM is destined for the same place as VESA and HD-VHS landed. Nice idea..... not adopted by the general public.

  • Seems Solid (Score:5, Informative)

    by farnsworth ( 558449 ) on Tuesday May 24, 2011 @09:07PM (#36234898)
    Seems like perfectly solid reasoning to me:

    Currently, it only supports a subset of the features that JPEG has. It lacks support for any color representation other than 4:2:0 YCrCb. JPEG supports 4:4:4 as well as other color representations like CMYK. WebP also seems to lack support for EXIF data and ICC color profiles, both of which have be come quite important for photography. Further, it has yet to include any features missing from JPEG like alpha channel support.

    [...]

    Every image format that becomes “part of the Web platform” exacts a cost for all time: all clients have to support that format forever, and there's also a cost for authors having to choose which format is best for them. This cost is no less for WebP than any other format because progressive decoding requires using a separate library instead of reusing the existing WebM decoder. This gives additional security risk but also eliminates much of the benefit of having bitstream compatibility with WebM. It makes me wonder, why not just change the bitstream so that it's more suitable for a still image codec?

    WebP, by Jeff Muizelaar [blogspot.com].

  • alpha transparency (Score:3, Informative)

    by edxwelch ( 600979 ) on Tuesday May 24, 2011 @09:11PM (#36234944)

    If webp supported alpha transparency it would be useful. png is a lossless format and therefore much bulkier. A png is normally 5 times bigger than jpg image. But jpg doesn't support transparency

  • Re:That's dumb. (Score:5, Informative)

    by Mekabyte ( 678689 ) on Tuesday May 24, 2011 @09:21PM (#36235012) Homepage
    As author of the Mozilla WebP patch, I can confirm that this was originally true. However, due to various shortcomings in design, WebP split off into its own codec library.
  • Re:Why? (Score:5, Informative)

    by tepples ( 727027 ) <tepples.gmail@com> on Tuesday May 24, 2011 @09:22PM (#36235020) Homepage Journal
    Anonymous Coward wrote:

    Why do we need yet another image format?

    If a new format 1. has an alpha channel, 2. has demonstrably better SSIM than JPEG, and 3. preserves Exif and ICC metadata, then it's superior to JPEG. In theory, WebP should have demonstrably because it's based on VP8 keyframes, while JPEG uses much the same technique as MPEG-1 keyframes. But it lacks an alpha channel, and it lacks Exif and ICC.

  • by petermgreen ( 876956 ) <plugwash.p10link@net> on Tuesday May 24, 2011 @09:32PM (#36235074) Homepage

    PNG is lossless

    More specifically it's a lossless representation of a single layer RGB image.

    better for photos then JPEG.

    For display of photos on the web the huge filesize advantages of JPEG outweigh the minor reduction in quality.

  • Re:Why? (Score:2, Informative)

    by enoz ( 1181117 ) on Tuesday May 24, 2011 @10:28PM (#36235406)

    JPEG uses much the same technique as MPEG-1 keyframes. But it lacks an alpha channel, and it lacks Exif and ICC.

    JPEG supports a plethora of metadata including Exif, IPTC, XMP and according to Wikipedia [wikipedia.org] also supports ICC.

  • Re:Interesting... (Score:5, Informative)

    by adolf ( 21054 ) <flodadolf@gmail.com> on Wednesday May 25, 2011 @01:22AM (#36236264) Journal

    Even Apple had to cave when it came to MP3 (they wouldn't sell it, but the iPod had to play it).

    Your history is backwards:

    The iPod first launched on October 23, 2001, and it played MP3s just fine at that time.

    The iTunes Music Store opened on April 28, 2003. Prior to this, Apple didn't sell content for the devices.

    Apple never "caved," they simply built an MP3 player which happened to be successful. Later on, they started selling content for it (in the arguably more space-efficient AAC format).

Suggest you just sit there and wait till life gets easier.

Working...