- From: David Humphrey <David.Humphrey@senecac.on.ca>
- Date: Tue, 15 Jun 2010 14:54:30 -0400
- To: Chris Grigg <chris@chrisgrigg.org>
- Cc: public-xg-audio@w3.org
> and this would be difficult to achieve in any interpreted/scripting language, across a broad range of client device capabilities. Based on the experience doing our implementation, I really encourage people to build demos to prove or disprove claims about what js can and can't do. People still tell me what I've already done is not possible, since js is too slow. I've got the code to prove otherwise. And we could do a lot more (I might do more to disprove some things I've read in here already). JS has an upper performance limit, there's no doubt. I'm just not sure it's where people think it is in all cases. It's also not static, especially if we can present quality test cases to the various JS impl folks (I've had good luck with this in a Mozilla context, for example). Dave
Received on Tuesday, 15 June 2010 21:37:08 UTC