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

My understanding is that Dart VM will be in Chrome soon.



http://www.chromium.org/blink#new-features has some detail about how we plan to add features to the platform. We're certainly hoping to be pretty transparent about how things get into Chromium.


That section states that you will make exceptions against compatibility with competing implementations under the following conditions:

1. That you propose a draft specification

2. That you're willing to discuss it with other implementors

3. That you've exhausted all other options

So let's take the example of Dart, and let's say every other browser engine says "no" to Dart. This policy seems to allow you to act unilaterally, against current interoperability, in this case as long as you put some indeterminate amount of effort to convince other implementors.

Is that a correct reading of it? If so, what good is the rest of the policy about striving for compatibility with other engines when you've given yourself an out when consensus doesn't fall your way?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: