Hacker News Reader

Comment by tomek2k1 | Hacker News Reader

Does not work in any browser except Safari and Chrome

But it is written using the Web Audio API, support for which is now available in Firefox nightly builds, for example. At the moment the FF builds do not support the OscillatorNode used by this library, but when they do this should work fine.

We're working hard on the spec and its test suite to make it easy for other browser vendors to support the API, so hopefully we'll see support for it in more browsers soon.

Disclaimer: I co-chair the W3C Web Audio WG.

We landed OscillatorNode support yesterday or something, and it kind of works just fine in Firefox. Kind of, because there is a _horrible_ noise before you press play and after the track finishes. I'm looking into it at the moment.

I think that should be labelled "does not work full stop".

I've had this rant before but WebKit is becoming the new IE6 and it's pissing me off as a Firefox and IE user.

It's a technical demonstration of the W3C WebAudio API. By your logic we shouldn't have great demos such as these because a subset of vendors haven't pulled their finger's out of their collective arses to implement a spec that's been around for a couple years.

Sorry you're pissed off, but your rant is directed at the wrong people. Go file bug reports with Mozilla and Microsoft instead of chastising someone for making something cool.

That's a little unfair. The spec was presented when it was already implemented in the browser by the spec authors. That's why they are so far ahead of the curve. Mozilla had a spec and implementation of another approach that predates the Web Audio API. Once the working group settled on what spec to go for then implementation started.

I don't like the comparison, because IE6 wasn't really ahead of its competition, yet WebKit simply gives you possibility to play with new APIs and not-yet-finished "standards", without waiting for them to become official standards (and already existing implementation helps to improve/fix them before getting final version).

I haven't checked that this is the case (i.e. whether making it work in Fx would be huge burden or even impossible), possibly not. Anyway, just saying.

IE6 introduced XmlHttpRequest, just one of the things where it was ahead of its competition.

It was IE5 AFAIR.

EDIT: And to be precise, XMLHttpRequest is Mozilla's naming that came later (after Microsoft's interface name: IXMLHTTPRequest). So you meant: ActiveXObject("Microsoft.XMLHTTP")

Reply on news.ycombinator.com