Linked by Thom Holwerda on Wed 19th May 2010 18:59 UTC, submitted by kragil
Internet Explorer This warrants a new post as far as I'm concerned, mostly because the original post is getting buried in updates and will soon drop below the fold. Microsoft has just announced it will support VP8 in HTML5 video in Internet Explorer 9, but only if the user has the DirectShow filter installed. Update: Yes, the updates keep on coming. Zencoder has added support for VP8. Update II: Zencoder's side project, video.js, offers a player that can fallback between h.264, OGG and VP8 on most browsers. Support for Android browsers is underway too. Update III: The H264 supporters' hardware argument for mobile is sounding moot too, since ARM explains on its blog that mobile devices with Cortex-A8 and Snapdragon processors "will be able to take advantage of WebM" through those chips' NEON SIMD engine.
Permalink for comment 425534
To read all comments associated with this story, please click here.
RE[4]: Thanks MS
by rhetoric.sendmemoney on Wed 19th May 2010 23:26 UTC in reply to "RE[3]: Thanks MS"
Member since:

Oh please. You are judging his logic but you just put your own spin on the same facts.
1) Writing an entire rendering engine would have been exponentially more expensive to develop and take years longer.
2) Apple did not pick KHTML because it was open source.
3) By your own admission Apple saw merit in KHTML _at minimum_ as a good base for Webkit.

While KHTML might not be as advanced as it is today without Webkit, Webkit would be a largely irrelevant curiousity without KHTML. It would be nothing more than another proprietary engine running in Apple's shroud of secrecy. Writing a rendering engine from scratch takes years of focused development - even for Apple. To devalue KHTML so implicitly is just emotional blindness.

Apple turned a solid open source project into a fine rendering engine. Both parties deserve equal credit, especially since one party didn't earn a dime off it.

Reply Parent Score: 4