New browser engines - what does that mean for our work on web audio / web midi

Hi all,

The past two days have been rich in announcements, notably the unveiling of work on both the Servo [1][2] and Blink [3] browser engines.

[1] https://github.com/mozilla/servo
[2] https://blog.mozilla.org/blog/2013/04/03/mozilla-and-samsung-collaborate-on-next-generation-web-browser-engine/
[3] http://www.chromium.org/blink

Is it too early to ask out loud what implications these will have on our work? I am assuming that it will mean that we will go from having two distinct implementations (modulo a few different ports) to having (at least) three.

Things I am wondering:
* How does this affect our current discussion on vendor prefixes?
* How does this affect the development of the webkit implementation of web audio and web midi?
* How does this affect the current development of web audio on gecko?

I understand this is a public mailing-list where some things can't be shared yet, and of course not all questions have answers yet. But it would be interesting to hear what members of the group can share of their understanding of the situation.

Thanks,
--
Olivier





-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------

Received on Thursday, 4 April 2013 11:47:37 UTC