On 2014-04-15, 5:34 PM, K. Gadd wrote:
Arguably if you wait for other vendors to expose VR before you do it, you'll end up having to implement a sub-standard proprietary API like you did with Web Audio. If you're first to the market (even with a prototype that's preffed off), you can exert a lot more pressure on how things turn out, IMO. As long as the web facing part of the API isn't tied to the open-but-not-free Oculus API, you can always swap out the underlying parts later while continuing to reap the benefits of being able to take design leadership on VR.
The crappiness of Web Audio as an API was partly because it was designed based on what a good sane C API would look like and marketed heavily by Google before anyone had looked at the API to decide whether it's good or not. Being first doesn't always imply being right. I trust that we'll try to do the right thing about the API, but that is not what Vlad is asking help for yet. :-)
Ehsan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
