Linked by Thom Holwerda on Wed 14th Mar 2012 19:37 UTC
Thread beginning with comment 510605
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2010-06-08
The situation was like that already for long time. So if you are saying that Mozilla's change in principal position is either caused by desperation about slow WebM adoption or by need to get hardware performance on mobile devices without hardware WebM decoding, then both arguments are not convincing to differ it from the situation on the desktop really. WebM was nowhere when it started, still Mozilla was strongly against promoting H.264. The most decisive factor here really is Google's desertion. Since Google was supposed to be a good ally, Mozilla was not alone. Now they stand alone against the dark empire of "non free". Will they able to pull it through?