This is such an ignorant comment. You're wrong, it's actually nothing like that. It's technical demonstration of edge W3C APIs, not something coded against proprietary APIs or around rendering engine bugs. It requires any browser that has implemented the W3C AudioContext API, which at this point only Chrome has implemented in a generally available release. But this doesn't quite fit into the 80 char constraint of HN link titles.
The difference is that someday this will also work in Firefox, Opera, and/or Safari -- perhaps even the mobile versions. It requires Chrome today, but it won't require Chrome forever.
