4 ms·
>> instead of using well established standards which are compatible with every browser That's the problem. Firefox isn't keeping up with standards.
by moron4hire 5y ago
>> instead of using well established standards which are compatible with every browser
That's the problem. Firefox isn't keeping up with standards.
- burnte 5y agoWhat standards are they significantly behind on? I seem to recall Fx being a prime mover on standards most of the time, not a laggard.
- sfink 5y agoFirefox is doing quite well with the standards. Chrome is implementing things beyond the agreed-upon standards. Which to some extent has to happen in order to advance standards, but that only works if the changes are agreed upon or at least not disagreed upon by other implementations. These days Chrome is forging ahead even in the face of disagreements (usually on grounds of privacy or security). And to be clear, Firefox is behind on the relevant standard here. Though even then, it's more nuanced than that: Mozilla is ok with prototyping it even though they would prefer for it to use a more secure mechanism -- see https://mozilla.github.io/standards-positions/#webrtc-insertable-streams https://mozilla.github.io/standards-positions/#webrtc-insert... From what I can tell, Mozilla is in the place of playing catch-up because the other players chose to forge ahead without resolving their objections. [Ok, "our objections". I work for Mozilla. Not in a relevant area until recently, but it looks like I will be doing some very relevant work starting as soon as I close this damn tab.]
- atatatat 5y agoJust fork Chromium and save yourself 5 years of angst.