W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

[Bug 17415] (JSWorkers): JavaScriptAudioNode processing in workers

From: <bugzilla@jessica.w3.org>
Date: Mon, 11 Jun 2012 15:22:55 +0000
To: public-audio@w3.org
Message-Id: <E1Se6SF-00011D-VB@jessica.w3.org>

Jussi Kalliokoski <jussi.kalliokoski@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |jussi.kalliokoski@gmail.com

--- Comment #5 from Jussi Kalliokoski <jussi.kalliokoski@gmail.com> 2012-06-11 15:22:55 UTC ---
While I agree that it's not a good idea to do time-critical heavy lifting like
audio on the main thread, sometimes there isn't much choice: emulators and
other virtual machines, ports of existing code (more possible but could be very
difficult as the original code may have strong shared state with the audio
code), and such.

These kind of programs are quite challenging as it is, I don't think a few bad
eggs should make the lives of those developers worse than it already is by
having to do expensive tricks like sending the audio data to the worker with
postMessage and maintaining the callback system themselves.

I always find these discussions about creating bad practices a bit frustrating,
people will make bad choices, no matter how well we design things. For me, it
doesn't mean that we shouldn't try to avoid making things so that developers
want to do bad things, but actively making actual use cases harder to keep some
people from making stupid decisions is counter-productive, IMHO.

You give them the rope, some will hang themselves, some will build a bridge.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 11 June 2012 15:23:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:59 UTC