5 ms·

Well yes, but technologically, it's the only non-KHTML descendant browser engine in development. Mozilla is working on the revenue issue, though it is a conside

by ripdog 7y ago

Well yes, but technologically, it's the only non-KHTML descendant browser engine in development. Mozilla is working on the revenue issue, though it is a considerable concern. The best thing we can do to help Mozilla is to simply use Firefox and try and bump its market share numbers up.

magicalhippo 7y ago
> he best thing we can do to help Mozilla is to simply use Firefox and try and bump its market share numbers up. And donate...
- ripdog 7y ago
  I won't say no, but these donations go to Mozilla Foundation and are used to advance their tech evangelism work, such as their successful lawsuit over net neutrality in the US. Mozilla Corporation develops Firefox with their income from sources like their contract with Google and other search engines. Donations are not used for Firefox dev.
  - magicalhippo 7y ago
    So what software is the Mozilla Foundation developing that's costing them over $200 million a year that isn't Firefox?
    - ripdog 7y ago
      Sorry, what? Mozilla Foundation doesn't do software development.
      - magicalhippo 7y ago
        Their financial statement says they do. https://www.mozilla.org/en-US/foundation/annualreport/2017/ https://www.mozilla.org/en-US/foundation/annualreport/2017/ The way it's worded it sounds like they do it through the Mozilla Corporation, which they own wholly own.
colejohnson66 7y ago
Genuine question: what are they doing to alleviate the issues of Gecko rendering compared to Blink? As I understand it, most developers target Chrome, so they make it work with Blink, not Gecko.
- ripdog 7y ago
  I don't think it's a major issue (yet?), but work around this area is tracked under the "Web Compatibility" product in Bugzilla. https://bugzilla.mozilla.org/buglist.cgi?product=Web%20Compatibility&bug_status=__open__ https://bugzilla.mozilla.org/buglist.cgi?product=Web%20Compa... Bugs are fixed where necessary, but I don't think they've stooped to implementing Chrome's bugs yet. Most of the work is social - reaching out to owners of websites which are broken in Firefox and asking them to fix them.
- commoner 7y ago
  Mozilla is using the a built-in add-on called Go Faster to resolve compatibility issues with poorly tested sites. https://github.com/mozilla/webcompat-addon https://github.com/mozilla/webcompat-addon https://wiki.mozilla.org/Compatibility/Go_Faster_Addon/Override_Policies_and_Workflows https://wiki.mozilla.org/Compatibility/Go_Faster_Addon/Overr... https://hacks.mozilla.org/2019/07/firefox-68-bigints-contrast-checks-and-the-quantumbar/ https://hacks.mozilla.org/2019/07/firefox-68-bigints-contras... The add-on uses data from WebCompat, and there are several ways you can report site issues: https://webcompat.com https://webcompat.com https://webcompat.com/contributors/report-bug https://webcompat.com/contributors/report-bug

by ripdog 7y ago

magicalhippo 7y ago

> he best thing we can do to help Mozilla is to simply use Firefox and try and bump its market share numbers up. And donate...

ripdog 7y ago
I won't say no, but these donations go to Mozilla Foundation and are used to advance their tech evangelism work, such as their successful lawsuit over net neutrality in the US. Mozilla Corporation develops Firefox with their income from sources like their contract with Google and other search engines. Donations are not used for Firefox dev.
- magicalhippo 7y ago
  So what software is the Mozilla Foundation developing that's costing them over $200 million a year that isn't Firefox?
  - ripdog 7y ago
    Sorry, what? Mozilla Foundation doesn't do software development.
    - magicalhippo 7y ago
      Their financial statement says they do. https://www.mozilla.org/en-US/foundation/annualreport/2017/ https://www.mozilla.org/en-US/foundation/annualreport/2017/ The way it's worded it sounds like they do it through the Mozilla Corporation, which they own wholly own.

colejohnson66 7y ago

Genuine question: what are they doing to alleviate the issues of Gecko rendering compared to Blink? As I understand it, most developers target Chrome, so they make it work with Blink, not Gecko.

ripdog 7y ago
I don't think it's a major issue (yet?), but work around this area is tracked under the "Web Compatibility" product in Bugzilla. https://bugzilla.mozilla.org/buglist.cgi?product=Web%20Compatibility&bug_status=__open__ https://bugzilla.mozilla.org/buglist.cgi?product=Web%20Compa... Bugs are fixed where necessary, but I don't think they've stooped to implementing Chrome's bugs yet. Most of the work is social - reaching out to owners of websites which are broken in Firefox and asking them to fix them.
commoner 7y ago
Mozilla is using the a built-in add-on called Go Faster to resolve compatibility issues with poorly tested sites. https://github.com/mozilla/webcompat-addon https://github.com/mozilla/webcompat-addon https://wiki.mozilla.org/Compatibility/Go_Faster_Addon/Override_Policies_and_Workflows https://wiki.mozilla.org/Compatibility/Go_Faster_Addon/Overr... https://hacks.mozilla.org/2019/07/firefox-68-bigints-contrast-checks-and-the-quantumbar/ https://hacks.mozilla.org/2019/07/firefox-68-bigints-contras... The add-on uses data from WebCompat, and there are several ways you can report site issues: https://webcompat.com https://webcompat.com https://webcompat.com/contributors/report-bug https://webcompat.com/contributors/report-bug