Hacker News new | past | comments | ask | show | jobs | submit login

This can be seen exceptionally when watching videos where some implementations prefer Flash. I often fall asleep to documentaries (maybe not a typical use case) and I've seen massive gains in battery life using Safari (using HTML5 video) vs. Chrome (using Flash). Granted, this isn't a fair comparison as one is using a "native" implementation and one is using Flash. But I've seen something like 250% gain in battery life – which sometimes means the difference between seeing the ending and not.

It's interesting watching one's projected battery life climb from 40m to 1h 40m simply by swapping one application for another. However, it's unfortunate some websites prefer Flash-based implementations over their native counterparts. Although this trend seems to be shifting in favor of those that are native. And I assume the smart folks at Google are taking note. YouTube, for example, has done a particularly spectacular job at adding AirPlay functionality to their HTML5 player.

(Disclaimer: I work for Apple)




Please bring Safari back to Windows, we're running out of options here :[.


Novice question, how does using "native" implementation rather than "Flash" reduces the wakeups calls?


My guess is that native HTML5 is just h.264, and most modern systems have a hardware decoder that would be much more efficient at decoding than a software implementation. Flash video is a wrapper around a number of codecs, and if the codec isn't h.264, then you're doing software decoding, which is far less efficient.


There is currently no good browser for apple. Safari (8.0.8) struggles with HTML5. Firefox (40.0.2) struggles with video/media of any sort and bogs down with multiple tabs. Chrome (44.0.2403.157 (64-bit)) drains your battery. I'm on a MacBook Pro (10.10.5, 13-inch, Early 2015). They are all uniformly disappointing.


>Safari (8.0.8) struggles with HTML5.

What?


No Stream API support for example

http://caniuse.com/#feat=stream


Struggles may have been the wrong verb. I meant this:

https://html5test.com/compare/browser/chrome-44/safari-8.0.h...

Straightforward things like pattern matching on form inputs

http://caniuse.com/#feat=input-color

http://caniuse.com/#feat=download


>pattern matching on form inputs

That's hardly "struggles", it's just a not very prominent feature that wasn't implemented, or not done properly.


Ok, but how do these affect someone during daily use? Is it _that_ much of a hindrance?


How does exactly Safari "struggle" with HTML5?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: