3 ms·

But independent browsers need this metric. Good luck convincing website owners to test against your non-chromium browser with 0.3% market share.

rollcat 1y ago
Twitch randomly blocks Chromium. (They don't even block the streams, only logins. I can watch, but not spend money. Perfectly reasonable.)
- tux3 1y ago
  Huh? That's crazy, I've never been blocked on Firefox, which is much smaller. And packed with privacy addons.
WD-42 1y ago
Okay but if everyone building the websites are using the browser with 0.3% market share it won't matter.
- nicce 1y ago
  They don’t. Most of the common web developers do what the managers and users require. Otherwise you are not providing value and using your time efficiently.
drdaeman 1y ago
I'm not tracking what's currently going on with the underwater portion of frontend iceberg. Are things still like it was in late '00s and early '10s, where browsers still had plenty of their unique implementation quirks and non-standard features, and plenty of sites were relying on those? Back in the day, it was not entirely unheard of having two significantly different frontend implementations - one for IE, another for Netscape, with quite unhealthy amounts of parser hacks to hide code from the browsers. Possibly naively, but I think it's not that bad nowadays? (At least it wasn't so in late '10s.) Some things are Chrome-only, or Apple-only, but I rarely see "not supported in your browser" - the majority of features is generally standards compliant, and all those newcomer engine problems (like in the article) are mostly because there's a lot to implement.
- nicce 1y ago
  It is not about what is supported now, but what will be supported in the future? Google is pushing most of the web standards and has a huge influence. Other, less used browsers must support them if they want to have any chance. You should ask that how many of the standard features are brought by someone else without huge influence of Google. If you cannot get anything new, when it is enough that Google says "no", then in reality there is only one browser.

rollcat 1y ago

Twitch randomly blocks Chromium. (They don't even block the streams, only logins. I can watch, but not spend money. Perfectly reasonable.)

tux3 1y ago
Huh? That's crazy, I've never been blocked on Firefox, which is much smaller. And packed with privacy addons.

WD-42 1y ago

Okay but if everyone building the websites are using the browser with 0.3% market share it won't matter.

nicce 1y ago
They don’t. Most of the common web developers do what the managers and users require. Otherwise you are not providing value and using your time efficiently.

drdaeman 1y ago

I'm not tracking what's currently going on with the underwater portion of frontend iceberg. Are things still like it was in late '00s and early '10s, where browsers still had plenty of their unique implementation quirks and non-standard features, and plenty of sites were relying on those? Back in the day, it was not entirely unheard of having two significantly different frontend implementations - one for IE, another for Netscape, with quite unhealthy amounts of parser hacks to hide code from the browsers. Possibly naively, but I think it's not that bad nowadays? (At least it wasn't so in late '10s.) Some things are Chrome-only, or Apple-only, but I rarely see "not supported in your browser" - the majority of features is generally standards compliant, and all those newcomer engine problems (like in the article) are mostly because there's a lot to implement.

nicce 1y ago
It is not about what is supported now, but what will be supported in the future? Google is pushing most of the web standards and has a huge influence. Other, less used browsers must support them if they want to have any chance. You should ask that how many of the standard features are brought by someone else without huge influence of Google. If you cannot get anything new, when it is enough that Google says "no", then in reality there is only one browser.