Mike Becky

Tag Archive for ‘HTML5’

YouTube Now Defaults to HTML5 Video ➝

I don’t think there’s a website on the planet that made extensive use of Flash on the scale that YouTube did, and now they’re defaulting to HTML5.

Simple Questions Regarding Chrome’s Dropping of H.264 ➝

John Gruber has published a list of simple questions regarding the removal of H.264 support from Chrome. My favorite of the questions:

Do you expect companies like Netflix, Amazon, Vimeo, Major League Baseball, and anyone else who currently streams H.264 to dual-encode all of their video using WebM? If not, how will Chrome users watch this content other than by resorting to Flash Player’s support for H.264 playback?

This is obviously an effort to push Google’s WebM codec. But, does Google expect WebM to succeed when Internet Explorer supports H.264 and H.264 alone? Remember, IE accounts for over 30% of browser market share.

Hulu on HTML5 ➝

In a recent Hulu weblog post Eugene Wei writes:

We continue to monitor developments on HTML5, but as of now it doesn’t yet meet all of our customers’ needs. Our player doesn’t just simply stream video, it must also secure the content, handle reporting for our advertisers, render the video using a high performance codec to ensure premium visual quality, communicate back with the server to determine how long to buffer and what bitrate to stream, and dozens of other things that aren’t necessarily visible to the end user. Not all video sites have these needs, but for our business these are all important and often contractual requirements.

I can understand their concerns about securing content. No matter how you feel about copy protection, I think we can admit that if you could easily download video from Hulu it would hurt ad sales for the site. And, unless we all start giving money directly to content producers, they’re going to need at least some of us to actually watch these ads.

But, let’s be honest this isn’t HTML5 vs. Flash, this is about being able to watch Hulu on the iPhone and iPad. And to be honest, I really think that experience would be better in a native application. Just imagine Hulu pushing icon badges to you letting you know that there’s a new episode of your favorite show. Now that would be fancy.

Goodbye Google Gears ➝

Gears API Blog:

If you’ve wondered why there haven’t been many Gears releases or posts on the Gears blog lately, it’s because we’ve shifted our effort towards bringing all of the Gears capabilities into web standards like HTML5. […] We will not be investing resources in active development of new features. Likewise, there are some platforms that would require a significant engineering effort to support due to large architectural changes.

Gears will not be supported in Safari for Snow Leopard or later, and they currently plan to support Firefox and Internet Explorer moving forward.

I was really excited about Google Gears when it was first announced back in 2007. But, it’s a different world now, HTML5 is the future and I’m glad the folks at Google are smart enough to admit it. I don’t expect Gears to stick around for too much longer.