Google Play Store: Browsing with Firefox is no longer supported on Android

Post by gcb0 » Tue, Feb 10, 2015, 11:17 PM UTC

nathanb wrote: post #202

gcb0 wrote: post #194

Earlier quoted context omitted.

i disagree. i think what we all must do is tell everyone exactly that. "don't use Google play store, it's like ie6. use fdroid and be happy". and then we all drop support to it, just like we dropped support to ie6 and it's bullying tactics, even though we own ajax to it, there's so much abuse one can take. do your part for free software. but yeah, i know that building your startup on top of a free software stack mean…

+1 because the existence of fdroid had not penetrated the rock under which I live before now.

Post by chris_wot » Wed, Feb 11, 2015, 4:47 AM UTC

drzaiusapelord wrote: post #108

oblio wrote: post #102

This is a dangerous slope. And I'm sad seeing many of the arguments here - a wild guess is that they've been made by people who weren't here (or have forgotten) the Microsoft/IE story. Soon it will become: "Why would they invest resources? Firefox is a niche browser, the return on investment is not justified". After all, Firefox's market share is dwindling. I really hope we're not slowly being boiled like the proverb…

Weren't we all applauding some startup that had a douche-bagy "We dont support IE" message on their site and everyone here was so excited about it. Now that the bell is tolling for Firefox, its a different story, eh? There's been this largely ridiculous "revenge of the geeks" after the IE6 days. Now we've fed so much fuel into that fire, that casually telling people to use different browsers is the norm. I'm not sayi…

Post by Chahat » Wed, Feb 11, 2015, 8:48 AM UTC

Post by jfoster » Wed, Feb 11, 2015, 12:01 PM UTC

dblohm7 wrote: post #200

johnkpush wrote: post #180

Earlier quoted context omitted.

It's browser vendors that are bearing the torch of interoperability and standards compliance. Unfortunately, most vendors are companies with their own agenda. To add to that, all companies and people interpret standards differently. Given this, it's no wonder we don't see consistent api implementation and behaviors between browsers. The aftermath of all of this falls on the developer's shoulders, which is why so many…

"When you start using a seemingly mature HTML5 api, and find that it doesn't work as expected in all browsers, what recourse does one have?" File bugs. Chromium and Firefox are not black boxes.

Post by john61 » Wed, Feb 11, 2015, 2:44 PM UTC

scholia wrote: post #204

kenbellows wrote: post #127

Earlier quoted context omitted.

There is potentially a critical difference here. The "We don't support IE" mini-movement was a reaction to Microsoft's refusal to use the web standards that every other major browser supported. In this case, it appears to me (admittedly without research) that Google's motivations must be different, and two possibilities spring to mind: (1) Google doesn't like the competition from Firefox or (2) the Play store uses no…

> a reaction to Microsoft's refusal to use the web > standards that every other major browser supported Take your points, but in fact, Microsoft didn't refuse to support web standards. IE6 was more standards-compliant than Netscape when it came out. The main problem was that Microsoft stopped developing browsers (for complicated reasons that must include the US anti-trust suits). That put it years behind in standards…