Live data from Hacker News

The irony of Apple homepage and Safari WebP support

mobilerank.co

1–10 of 75 posts

Re: The irony of Apple homepage and Safari WebP support

#4
Firstly, i don't get what apple has to gain by not supporting webp... Nevertheless:

The screenshot puzzles me, it shows two assets, and states that compressing these by an extra ~ 250 kb would save 2 seconds. Maybe on very slow connections?

Also

> Lack of proper support for [...] web notifications on mobile

I can do without these i guess

Re: The irony of Apple homepage and Safari WebP support

#6

At this point, I don't think it's too fringey a conspiracy theory that Apple is opposed to the advancement of web technology, while trying to plausibly appear to be in favor of it. Their motive would be obvious. Keep the native app experience superior.

That's pretty fringey. Given that Apple devices still use the web a lot, including inside apps.

Re: The irony of Apple homepage and Safari WebP support

#8
post #3

At the expense of quality, at least it was Apple's argument against supporting webp. And no, they didn't ignore it, it was included in one of the previous betas of macOS and iOS and removed later. Don't remember which.

Huh, I didn’t know this. Doing a bit of Googling, looks like it was iOS 10 / macOS Sierra.

https://www.macobserver.com/news/webp-comes-ios-10-macos-sie...

Edit: Now I kind of want to see if I can hack in support on other OS X versions by copying files around...

Re: The irony of Apple homepage and Safari WebP support

#10

At this point, I don't think it's too fringey a conspiracy theory that Apple is opposed to the advancement of web technology, while trying to plausibly appear to be in favor of it. Their motive would be obvious. Keep the native app experience superior.

That's pretty fringey. Given that Apple devices still use the web a lot, including inside apps.

Easily explained! Apple prefers you to use native widgets to make your app harder to port.
Post reply on HN