4 ms·

Mozilla needs to stop focusing on side projects like Pocket and get back to the actual browser.

agumonkey 5y ago
Honest question, what is there to fix in Firefox ? Web is getting increasingly integrated in real life so bridges and apps may take the spotlight (just a guess).
- whywhywhywhy 5y ago
  >Honest question, what is there to fix in Firefox ? If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it. Not that I condone that, but it's what I experience working with dev teams the past few years they all just complain that features are missing from Chrome so it will be too much work to test/support FF.
  - genezeta 5y ago
    > If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it. You'll surely meet a lot of people doing what you mention. I would bet most of them are young enough to not have gone through the so-called "browser wars" [1], at least what they now call the first one, the one that ultimately led to the creation of Firefox. Their attitude does not mean at all that there's something actually broken in Firefox, just that it is so much easier -and lazier- supporting a single browser's quirks and ignoring the rest. Even if that means discarding standards and compatibility. Specially if it means that, because you will take advantage of those particularities. [1] https://en.wikipedia.org/wiki/Browser_wars https://en.wikipedia.org/wiki/Browser_wars
    - whywhywhywhy 5y ago
      I was doing front end dev in the IE6/5.5 era so yeah it’s incredibly frustrating to hear it over and over when you’re right deep down it’s all excuses because supporting one browser is less effort.
  - agumonkey 5y ago
    I wonder what APIs are so late in firefox that devs have trouble supporting it. (honest question). I was under the impression that most things were stable or that most major browsers implemented things at a similar pace.
  - CivBase 5y ago
    > If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it. This mentality is exactly why Internet Explorer was dominant for so long. Embrace, Extend, Extinguish. There are many differences between 2000s Microsoft and 2020s Google but there are also quite a few similarities, even down to funding their opposition to avoid the appearance of a monopoly.
- _Algernon_ 5y ago
  Getting extensions as customizable as they were before the great purge? They promised replacement-APIs with the new extensions system which they still haven't delivered.

Honest question, what is there to fix in Firefox ? Web is getting increasingly integrated in real life so bridges and apps may take the spotlight (just a guess).

whywhywhywhy 5y ago
>Honest question, what is there to fix in Firefox ? If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it. Not that I condone that, but it's what I experience working with dev teams the past few years they all just complain that features are missing from Chrome so it will be too much work to test/support FF.
- genezeta 5y ago
  > If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it. You'll surely meet a lot of people doing what you mention. I would bet most of them are young enough to not have gone through the so-called "browser wars" [1], at least what they now call the first one, the one that ultimately led to the creation of Firefox. Their attitude does not mean at all that there's something actually broken in Firefox, just that it is so much easier -and lazier- supporting a single browser's quirks and ignoring the rest. Even if that means discarding standards and compatibility. Specially if it means that, because you will take advantage of those particularities. [1] https://en.wikipedia.org/wiki/Browser_wars https://en.wikipedia.org/wiki/Browser_wars
  - whywhywhywhy 5y ago
    I was doing front end dev in the IE6/5.5 era so yeah it’s incredibly frustrating to hear it over and over when you’re right deep down it’s all excuses because supporting one browser is less effort.
- agumonkey 5y ago
  I wonder what APIs are so late in firefox that devs have trouble supporting it. (honest question). I was under the impression that most things were stable or that most major browsers implemented things at a similar pace.
- CivBase 5y ago
  > If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it. This mentality is exactly why Internet Explorer was dominant for so long. Embrace, Extend, Extinguish. There are many differences between 2000s Microsoft and 2020s Google but there are also quite a few similarities, even down to funding their opposition to avoid the appearance of a monopoly.
_Algernon_ 5y ago
Getting extensions as customizable as they were before the great purge? They promised replacement-APIs with the new extensions system which they still haven't delivered.