News for hackers. Stuff that matters.

A comment on Please consider not adopting Google WebComponents. Parent comment

Re:Please consider not adopting Google WebComponents by cmroanirgo on Tuesday March 17, 2020 @04:52PM (#22610284)
How do you mean that Firefox is struggling? It is not my experience this is so. Everyone around me is ditching Chrome for Firefox.

Firefox is also ahead in a few areas too: containerisation & privacy. It's also now the default browser on a few oses.

To me this does not indicate struggling at all.

[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by SEJeff on Tuesday March 17, 2020 @05:20PM (#22610576)
https://gs.statcounter.com/browser-market-share

Chrome: 65.54%

Firefox: 4.58%

Perhaps your sample size of people around you is too small?

[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by kybernetikos on Tuesday March 17, 2020 @05:32PM (#22610694)
You might well be right, but I, along with lots of other firefox users run extensions like NoScript which blocks 3rd party javascript unless explicitly whitelisted, so I expect a much higher proportion of firefox users probably don't show up on analytics packages (which is how statcounter stats are generated). DuckDuckGo Privacy essentials plugin also blocks statcounter, as I'm sure do many other privacy related plugins.

Even if you are a firefox user who doesn't use third party plugins, firefox itself will block statcounter if you have enhanced tracking protection turned on. I couldn't find a similar setting in Chrome.

[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by Sohcahtoa82 on Wednesday March 18, 2020 @07:00PM (#22622368)
Unless you're spoofing your User-Agent string, servers still know what browser you're using. You don't need to be running client-side analytics scripts for browser market measurements.
[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by kybernetikos on Wednesday March 18, 2020 @07:09PM (#22622459)
Sure, but that's not how statcounter or most advanced analytics packages work.

Your browser doesn't make a request to the analytics server if you're blocking it, so while the content server might know the user agent, the analytics server generally doesn't.

[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by w0m on Wednesday March 18, 2020 @10:53AM (#22617280)
I'd think it's a fairly safe bet that noscript users aren't a statistically significant part of total web users
[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by hvis on Tuesday March 17, 2020 @06:05PM (#22611026)
The marketshare might not be great, but it's doing just fine technology-wise. No problem in "maintaining a working web browser" there.
[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by SEJeff on Tuesday March 17, 2020 @06:10PM (#22611076)
Oh the tech in firefox is amazing, I'm just pointing out the marketshare is pretty lopsided for Chrome over Firefox.

It isn't as though there is actually a mass defection from Chrome to Firefox outside of a very small number of people.

[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by toper-centage on Wednesday March 18, 2020 @03:41AM (#22614450)
How many people are 4.5% of the Internet though? Would you close a project because it only has a couple hundred million daily users? Would you cal it a failure?
[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by to11mtm on Tuesday March 17, 2020 @05:04PM (#22610405)
My understanding is that they still struggle from a finance and ops perspective. Doesn't matter how good your product is if you can't keep the doors open...
[ Parent | on HN ]
Re:Please consider not adopting Google WebComponents by pjmlp on Wednesday March 18, 2020 @02:33AM (#22614183)
Firefox has long stop being a requirement on the acceptance criteria for Web project delivery.

I keep testing it, because it has been my favourite browser all the way back to Netscape days.

[ Parent | on HN ]