11–20 of 88 posts
None of the things listed as "not currently planned" are big surprises, though seeing WebRTC there is very disappointing. I've never seen "Object RTC" before, is it a competing effort, or a restandardization effort?
They are comparing IE to other real modern browsers - it's rather surprising to see. Like saying "The competitors are far ahead, here what they already do and we don't and out of that what we plan to do next and what not.".
I'm bewildered by the many "under consideration" entries. When all the other major players support something, and you want to be taken seriously, why aren't you throwing more engineers at the problem?
(I work for IE)
heheh. This website has a hard dependency on chromestatus.com.
Would be nice to know if they plan on implementing special handling for asm.js. This info is nowhere on this chart.
None of the things listed as "not currently planned" are big surprises, though seeing WebRTC there is very disappointing. I've never seen "Object RTC" before, is it a competing effort, or a restandardization effort?
Object RTC is developed by a community group at the W3C. It includes people from Google, Microsoft and a number of telecom companies, amongst others http://www.w3.org/community/ortc/
I'm bewildered by the many "under consideration" entries. When all the other major players support something, and you want to be taken seriously, why aren't you throwing more engineers at the problem?
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)
None of the things listed as "not currently planned" are big surprises, though seeing WebRTC there is very disappointing. I've never seen "Object RTC" before, is it a competing effort, or a restandardization effort?