- From: Alistair MacDonald <al@bocoup.com>
- Date: Mon, 18 Oct 2010 16:50:48 -0400
- To: David Humphrey <David.Humphrey@senecac.on.ca>
- CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, public-xg-audio@w3.org
Dave, Silvia, I see what you mean, apologies for missing that. Al On 10/18/2010 04:46 PM, David Humphrey wrote: >> This idea has been brought up by quite a few people I have talked to at >> Web Audio workshops. The general consensus from JavaScript developers, >> seems to be that this is a good idea to have some core functions added >> to the JavaScript Math object. > >> >>> Has the group ever considered creating a maths JavaScript library for >>> which hardware support can be implemented and making that generally >>> available to the Web browser rather than creating audio-specific >>> filters? It was a question I was asked recently when discussing the > > Al, it seems to me that Silvia is saying something slightly different, > namely, creating a JS lib vs. adding things to Math directly. Once > created, such a lib could be optimized heavily in the JS > implementations, and/or merged into Math or wherever. > > I think this sort of approach is ideal, notwithstanding Chris' reply > that it misses cases where state matters--I'd argue that there are > still many cases where having access to such a lib would be helpful. > I know from experience that getting JS like this heavily optimized can > be done, and that these devs are eager for such real-world examples. > > I also think that there will be cross over with other non-audio > domains, and leveraging this work across them makes the most sense to me. > > Dave
Received on Monday, 18 October 2010 20:51:25 UTC