Re:Chrome is deploying HTTP/3 and IETF QUIC
by shadowgovt on Wednesday October 07, 2020 @04:27PM
(#24712343)
Sub-10% market share is a problem for them.
It's enough of a skew that when rendering errors crop up, product managers have to decide how many eng-hours it's worth to chase down the small implementation difference between Chromium and Gecko to snag 1 in 10 potential lost visitors, instead of throwing a UA-sniffing "best viewed in Chrome" banner on the page and calling it a day.
Being a rarely-used browser is a negative feedback loop for compatibility, regardless of what standards say (because standards are often too loose to guarantee full interoperability in all corner cases; they rarely give performance constraints and often don't consider all possible combinations of feature use).
Re:Chrome is deploying HTTP/3 and IETF QUIC
by mrec on Wednesday October 07, 2020 @05:24PM
(#24712909)
Agree on all points. It's not quite as deadly as back in the old browser wars, because HTML5 is much better specified than its predecessors, but it's definitely a major problem.
It's enough of a skew that when rendering errors crop up, product managers have to decide how many eng-hours it's worth to chase down the small implementation difference between Chromium and Gecko to snag 1 in 10 potential lost visitors, instead of throwing a UA-sniffing "best viewed in Chrome" banner on the page and calling it a day.
Being a rarely-used browser is a negative feedback loop for compatibility, regardless of what standards say (because standards are often too loose to guarantee full interoperability in all corner cases; they rarely give performance constraints and often don't consider all possible combinations of feature use).