|
|
|
|
|
by Aissen
4897 days ago
|
|
So Apple dug a hole by: - not allowing iOS to play videos in-DOM. - deciding not to support WebM, so Firefox users can't see their videos. And now others are following them by helping to dig deeper in a vastly inefficient way of displaying moving images ?
What could previously be offloaded to dedicated engines is now going to burn the CPU via JS. Hum, now that's gonna work… |
|
I don't see this as a MP4/WebM replacement (compared to which it is effectively inefficient) but a GIF replacement (plus it's scriptable and hackable in a number of interesting ways). I wish it were a real, self-contained file format, but APNG completely failed to displace GIF.
It's a hack, but it solves a real problem and it opens a venue for something less hackish.
Also, it's simple enough any developer can understand the algorithm, there's no patent looming over, no complex codec infrastructure (however layered away), and it's using only HTML/CSS/JS.