4 ms·

I don't like WebP because it's either it or HW accelerated browsing - latter I like a tad more because it saves me a bit of battery juice on my laptop.

TazeTSchnitzel 8y ago
There's the same problem with Google insisting on VP8/9 for YouTube in Chrome. If your Mac only supports h.264 in hardware you'll get better battery life in Safari.
- xvilka 8y ago
  Obviously it is a problem with Apple, not Google. People should just push it more to do the job.
  - TazeTSchnitzel 8y ago
    I don't think Google are free of responsibility. They are prioritising their lower bandwidth over the user's better power usage.
    - vetinari 8y ago
      Apple has a bigger share of the blame. They purposely ignore any codec that is outside of their favorites, even if the hardware they ship does support it (i.e. Intel) or doesn't need any hardware support (Vorbis, Flac). On the other hand, they are quick to support any codec, that is problematic to implement elsewhere.
- vosper 8y ago
  There's a Chrome extension that forces YouTube to stream h.264 https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal?hl=en https://chrome.google.com/webstore/detail/h264ify/aleakchihd...
- acdha 8y ago
  They also try it in Firefox but fortunately you can disable webm/webp in about:config and get better battery life and image quality.
RBO2 8y ago
HEIF (based on HEVC and support on MacOS/iOS + Android + Windows) is already way better than JPEG. It also provides HW acceleration. HEIF is made by MPEG. HEIG is extensible (see AVIF fusing the AV1 royalty-free codec). Also an application format (MIAF) will ensure interoperability. While waiting for native browser support, some js implementation would do the job. What else?
- xvilka 8y ago
  Isn't it a patented algorithm? So it is practically useless.
  - RBO2 8y ago
    I agree with you but hey JPEG also had its own patent issues (https://en.wikipedia.org/wiki/JPEG#Patent_issues https://en.wikipedia.org/wiki/JPEG#Patent_issues).
- zokier 8y ago
  > HEIF (based on HEVC and support on MacOS/iOS + Android + Windows) is already way better than JPEG. It also provides HW acceleration. Formats do not provide HW acceleration, implementations do. And so far there is zero HW accelerated HEIF implementations for the web.
  - jsjohnst 8y ago
    > And so far there is zero HW accelerated HEIF implementations for the web. You sure of that? Apple[1] and Qualcomm[2] might argue otherwise. [1] https://developer.apple.com/videos/play/wwdc2017/513/ https://developer.apple.com/videos/play/wwdc2017/513/ [2] https://techreport.com/news/34306/qualcomm-snapdragon-855-spreads-its-wings-for-the-5g-future https://techreport.com/news/34306/qualcomm-snapdragon-855-sp...
  - RBO2 8y ago
    I don't know who downvoted you but you're correct. The point is that most devices embed an HEVC hardware decoder.

TazeTSchnitzel 8y ago

There's the same problem with Google insisting on VP8/9 for YouTube in Chrome. If your Mac only supports h.264 in hardware you'll get better battery life in Safari.

xvilka 8y ago
Obviously it is a problem with Apple, not Google. People should just push it more to do the job.
- TazeTSchnitzel 8y ago
  I don't think Google are free of responsibility. They are prioritising their lower bandwidth over the user's better power usage.
  - vetinari 8y ago
    Apple has a bigger share of the blame. They purposely ignore any codec that is outside of their favorites, even if the hardware they ship does support it (i.e. Intel) or doesn't need any hardware support (Vorbis, Flac). On the other hand, they are quick to support any codec, that is problematic to implement elsewhere.
vosper 8y ago
There's a Chrome extension that forces YouTube to stream h.264 https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal?hl=en https://chrome.google.com/webstore/detail/h264ify/aleakchihd...
acdha 8y ago
They also try it in Firefox but fortunately you can disable webm/webp in about:config and get better battery life and image quality.

RBO2 8y ago

HEIF (based on HEVC and support on MacOS/iOS + Android + Windows) is already way better than JPEG. It also provides HW acceleration. HEIF is made by MPEG. HEIG is extensible (see AVIF fusing the AV1 royalty-free codec). Also an application format (MIAF) will ensure interoperability. While waiting for native browser support, some js implementation would do the job. What else?

xvilka 8y ago
Isn't it a patented algorithm? So it is practically useless.
- RBO2 8y ago
  I agree with you but hey JPEG also had its own patent issues (https://en.wikipedia.org/wiki/JPEG#Patent_issues https://en.wikipedia.org/wiki/JPEG#Patent_issues).
zokier 8y ago
> HEIF (based on HEVC and support on MacOS/iOS + Android + Windows) is already way better than JPEG. It also provides HW acceleration. Formats do not provide HW acceleration, implementations do. And so far there is zero HW accelerated HEIF implementations for the web.
- jsjohnst 8y ago
  > And so far there is zero HW accelerated HEIF implementations for the web. You sure of that? Apple[1] and Qualcomm[2] might argue otherwise. [1] https://developer.apple.com/videos/play/wwdc2017/513/ https://developer.apple.com/videos/play/wwdc2017/513/ [2] https://techreport.com/news/34306/qualcomm-snapdragon-855-spreads-its-wings-for-the-5g-future https://techreport.com/news/34306/qualcomm-snapdragon-855-sp...
- RBO2 8y ago
  I don't know who downvoted you but you're correct. The point is that most devices embed an HEVC hardware decoder.