▲ 640 ▼ Why do companies love chrome so much? (files.catbox.moe) submitted 2 years ago* by yoz@aussie.zone to c/mildlyinfuriating@lemmy.world 138 comments fedilink hide all child comments
[–] Venator@lemmy.nz 17 points 2 years ago (2 children) It still doesn't explain all the extra work of detecting and intentionally blocking firefox... permalink fedilink source parent hideshow 4 child comments replies: [–] tal@lemmy.today 4 points 2 years ago I expect that they had something break on it and decided that it wasn't worth the time spent fixing it, so they just blocked it so more users didn't run into it. A simple message may be annoying to them, but at least they have a straightforward workaround then. I mean, don't get me wrong, I use Firefox on both mobile and desktop, but it's not too hard to see why they'd do a cost/benefit analysis like that. No one company is in the business of trying to do antitrust work, to avoid a browser monopoly, and that'd be the reason why it'd be important to have competing browsers. permalink fedilink source parent [–] Nighed@sffa.community 3 points 2 years ago Something didn't work on Firefox and the dev didn't get permission to work out how to fix it as it was uneconomical compared with just disabling firefox permalink fedilink source parent
[–] tal@lemmy.today 4 points 2 years ago I expect that they had something break on it and decided that it wasn't worth the time spent fixing it, so they just blocked it so more users didn't run into it. A simple message may be annoying to them, but at least they have a straightforward workaround then. I mean, don't get me wrong, I use Firefox on both mobile and desktop, but it's not too hard to see why they'd do a cost/benefit analysis like that. No one company is in the business of trying to do antitrust work, to avoid a browser monopoly, and that'd be the reason why it'd be important to have competing browsers. permalink fedilink source parent
[–] Nighed@sffa.community 3 points 2 years ago Something didn't work on Firefox and the dev didn't get permission to work out how to fix it as it was uneconomical compared with just disabling firefox permalink fedilink source parent