| |||||||||||||
More about the Chrome HTML Video Codec Change (The Chromium Blog)More about the Chrome HTML Video Codec Change (The Chromium Blog)Posted Jan 17, 2011 12:14 UTC (Mon) by drag (subscriber, #31333)In reply to: More about the Chrome HTML Video Codec Change (The Chromium Blog) by krake Parent article: More about the Chrome HTML Video Codec Change (The Chromium Blog)
> I didn't get that part. My understanding is that very specific data processing, e.g. media decoding, is first implemented in software to be easily deployable to the mass market even if it more efficient to be implemented in hardware.
The hardware you talk about doesn't exist. That's what I mean. I am sure that it's all fine and dandy in some abstract theoretical sense.
Remember the problem domain here: we are looking for a flash replacement. I know I am in fantasy land also, but it's just really speculation. It's probably a horrible idea to try to obfuscate decryption in javascript, but requiring people to purchase new hardware is even less likely to work.
(Log in to post comments)
More about the Chrome HTML Video Codec Change (The Chromium Blog) Posted Jan 18, 2011 11:51 UTC (Tue) by krake (subscriber, #55996) [Link] The hardware you talk about doesn't exist. That's what I mean.I see. As I said, my impression was that hardware gets replaced at some point by newer one, introducing capabilities formerly available only in software. But I might be mistaken and all graphics chips always had video decoding in them, even for codecs that didn't exist yet. As a software engineer I surely would appreciate some of that fairy dust these hardware engineers seems to have at their disposal, being able to deploy algorithms before they are invented.
|
|||||||||||||