Ah,yes, good suggestion to add to our list on the site. Look for an update soon from our JS engine (Chakra) team's plan.

Thanks for such a fast reply! :) I'm quite happy with Microsoft's recent push towards openness.

One additional suggestion: Perhaps you could also include a rationale on why a specific feature is not planned to be implemented: e.g. WebRTC. (Though I can anticipate this might not be feasible to do for strategic / management reasons.)

Yep, and we're already chatting with the Chrome team on how browsers can collaborate on this type of data. We encourage people to use our data too. It's openly licensed.

You can use CORS to access the data at http://status.modern.ie/features :)

That's great!

This is good for sites like caniuse.com, so kudos.

If feature status were a Facebook relationship status, many might say "it's complicated." ;-) Most of the time, it's not actually a question of engineering resources. Stay tuned as we update more and more stuff to "In Development".

(I work for IE)

For what it's worth, it does look like things are moving in the right direction, so I hope the trend continues!

I'm curious--does this imply internal-politics problems (e.g. getting other departments to expose, and possibly backport, APIs that Chakra needs to consume to do the features), or just weird engineering challenges specific to the Chakra codebase?

I could see some conflicts of interest issues too. (e.g. implementing WebRTC could be against their interests - since Microsoft owns Skype, they might not want to lower the barrier of entry to a competitor.)

Microsoft are contributing to Object RTC, so I see this as unlikely.

In the past when they've spoken about why they delayed implementation it was often due to security issues (e.g. Webgl) or due to the standards proposal not being mature enough and them being worried that supporting it would lock in a bad version of the spec because people would build code on top.