Live data from Hacker News

The irony of Apple homepage and Safari WebP support

mobilerank.co

71–75 of 75 posts

Re: The irony of Apple homepage and Safari WebP support

#71
post #35

Earlier quoted context omitted.

1) “real world” cellular speeds at 30mbps? That sounds ludicrous to me. Maybe in America, definitely not in many countries across the world. 2) I don’t know a lot of people who are repeat visitors to apple.com. Mentioning the fact that the time is initial load time would be redundant.

> Maybe in America I'd say maybe outside America. Our cell service is pretty terrible if you leave major metropolitan areas, or if you try to actually use your "unlimited" data.

It’s inconsistent.

I live in rural Arkansas, and typical get about 50Mpbs via LTE in a hammock on the shore of the lake.

Re: The irony of Apple homepage and Safari WebP support

#72
post #64
post #51

Earlier quoted context omitted.

Apple would paid more for HEVC royalty than they receive, or a break even. I doubt royalty payment is an incentive of any kind to Apple. But much rather patent protection.

I work in video streaming business and I haven't seen anything to support this (if anything, they were exempt from royalties from their own patent pool), can you please link something that confirms this?

I think for Clarity I need some explaining. I dont have any hard data or fact, and I doubt anyone would have because of the sensitive nature.

But it is just some Numbers from Facts and Data put into to it and guess work.

If we look into the list of patents from HEVC from three patents pool, along with those missing such as Technicolor, the list from Apple is comparatively very tiny. As a matter of fact I would be surprised if they even get 2% from it given hundreds of companies are in the license pool.

Lets assume Velos Media is in good faith ( FRAND ) and charges similar to MPEG-LA and HEVC Advance, the total is estimated to be capped at roughly $100M per Enterprise annually. Despite a huge market increase in volume since H.264 era, the amount of Consumer Electronics companies ( Enterprise ) is actually not growing. While we are shipping ~1.2B Smartphone every year, ( A market that doesn't even exist during H.264 invention ) Huawei, Apple, Samsung represent over 50% of the Smartphone unit volume already. Top 10 vendor represent close to 90%. Once you factor in Tablet, PC, are in similar situation and many overlap ( since they are by the same Enterprise and count towards the cap ). The total addressable market from HEVC patents is at best $3B from large volume vendor ( $100M Cap x 30 Enterprise ) . You tie in the loose end from other electronics, Blu Ray disc at $2B per year. You are looking at a Total of ~$5B.

Ignoring the 2% Apple exempt from their own products and they actually paid 100M annually. $100M is exactly within the 2% they received from ~5B pool.

Generally Speaking in Reality Apple has many cross licensing agreement with like Samsung, Qualcomm and LG etc they are highly unlikely to be paying anywhere close to the Cap as they will all be exempt from it. And Apple would also not be getting anywhere close to 2% mark, but the argument is still the same.

Re: The irony of Apple homepage and Safari WebP support

#73
post #65

This is only one half of the story. Given the increased network bandwidth, decoding speed matters. And here, JPEG is much faster. Also note that the JPEG decompression algorithms are highly optimized and coded in assembly language, and there are maybe even hardware decoders. On android: WebP 66% less file size than JPG, 267% more time to decode. WebP 38% less file size than JPG, 258% more time to decode. WebP 89% les…

On Android, JPG decoder lib may or may not use a DSP on Qualcomm SoCs, WebP doesn't have any hardware decoding support. Any size gains will be much more noticeable in the context of network transmission.

Which comes back to people having good phones most probably will have better internet and people habing cheap phones will have less good internet.

So you‘ll lose time either on transfer or decoding.

Re: The irony of Apple homepage and Safari WebP support

#74

Earlier quoted context omitted.

That argument could be used for Qt, GNOME, macOS, or Windows. And besides, React Native is a thing.

Qt and GNOME are released by an organization that also maintains a popular browser. Microsoft recently chromified their flagship browser (despite my personal feelings on the matter). I could be wrong, but I don't think React Native gets any support from Apple.

> Qt and GNOME are released by an organization that also maintains a popular browser.

I think you meant "aren't"?

Re: The irony of Apple homepage and Safari WebP support

#75
post #25

Earlier quoted context omitted.

There is webpjs I think. http://webpjs.appspot.com/ Basically if a browser does support webp, the script does nothing, but otherwise I think this script ends up supporting the image via javascript.

Please don’t drain my battery with crap like this when my phone has dedicated hardware for JPEG decoding.

That script won't even run unless it's on a browser which doesn't support webp.

I don't have to support ios/safari.

Post reply on HN