On Thu, May 24, 2012 at 10:34 AM, Chris Wilson <cwilso@google.com> wrote: > I get that as a replacement for <audio src="foo.mp3">, the Web Audio API > is not a good solution. If all you really want (as the Audia sample page > seems to) is a different way to say <audio src="foo.mp3">, you are barking > up the wrong tree. But that isn't our use case set. > I agree. The HTML5 media element API is a perfectly adequate API for simply playing event-driven sounds with low latency (including preloading sounds). That Audia library is simply a workaround for media element implementation issues in Chrome (many of which occur in other browsers too). Ideally Audia would go away by us browser vendors fixing media element implementations, without new API. On the other hand, I agree with Marcus that, all other things being equal, having functionality in JS libraries is *less* complex than having it in browsers, for both authors and browser implementors. Implementors don't have to worry about specifying and interoperably implementing the functionality. Authors don't have to worry about interoperability failures and have a lot more freedom to customize the functionality to their needs. Rob -- “You have heard that it was said, ‘Love your neighbor and hate your enemy.’ But I tell you, love your enemies and pray for those who persecute you, that you may be children of your Father in heaven. ... If you love those who love you, what reward will you get? Are not even the tax collectors doing that? And if you greet only your own people, what are you doing more than others?" [Matthew 5:43-47]
Received on Thursday, 24 May 2012 00:46:05 UTC