4 ms·
I don't think anybody's saying the issue is technically infeasible to fix or work around. They just haven't had anybody to spend engineering time doing so yet.
by Intralexical 2y ago
I don't think anybody's saying the issue is technically infeasible to fix or work around.
They just haven't had anybody to spend engineering time doing so yet. Perhaps:
https://codetribute.mozilla.org/projects/fenix https://codetribute.mozilla.org/projects/fenix
https://firefox-source-docs.mozilla.org/setup/contributing_code.html https://firefox-source-docs.mozilla.org/setup/contributing_c...
We may disagree with Mozilla's priorities, but they do have finite resources. E.G. Should the extensions API have been delayed even more than it already was, to first build this separate `about:config` launcher as a kludge?
They're not being wilfully bullheaded in this case, is what I mean. The "P5"/"Enhancement" Bugzilla issue is open, but unassigned.
- AnthonyMouse 2y ago> They just haven't had anybody to spend engineering time doing so yet. But this has been the other major criticism of Mozilla. They take the money they get from Google and spend it on not-Firefox when Firefox market share should be their top priority, because if that number goes to zero they're defunct.