Hacker News new | past | comments | ask | show | jobs | submit login

One word: w3c.

I've said it before, I'll say it again: it exists in a vacuum, and is run by people who have never done any significant work on the web, with titles like "Senior Specifications Specialist". Huge chunks of their work is hugely theoretical (note: not academical, just theoretical) and have no bearing on the real world.




The Web Audio API was the work of the Chrome team, not the W3C in isolation. I'm right there with you as far as W3C criticism is concerned, but they don't deserve the blame in this case.


It was really the work of Chris Rogers. If more core Chrome people had been involved, I suspect things would have worked out better.


> work of the Chrome team

Indeed. Because people who do browser internals and never do any web development are a good fit to create APIs for web developers




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: