News for hackers. Stuff that matters.
Re:Teaching machines to triage Firefox bugs by yoasif_ on Tuesday April 09, 2019 @04:22PM (#19618577)
I have reported 238. 45 have been fixed, 27 I later marked as "works for me" (so fixed by some other change in Firefox). 57 were duplicates of other bugs (and I'm not looking to see how many of those were fixed).

Things do get fixed, but it is a big project with not a huge amount of staff.

Re:Teaching machines to triage Firefox bugs by microcolonel on Tuesday April 09, 2019 @06:20PM (#19619561)
If I had more time on my hands this would be okay, but when I'm developing web pages/applications, I end up using workarounds because Firefox is so often not compliant, rather than suddenly becoming a qualified Gecko developer and finding the time to fix some almost-Netscape-era bug.

The problems mount up over the years while it seems that meanwhile, Mozilla has a lot of frills and luxuries on the budget as an organization, when the core product is generally lacking in terms of compliance and quality.

It's frustrating, because I want to like Mozilla, but their browser is the most work to develop for, and the least fun to use (in my case in particular, since Firefox is generally worse on Linux than on Windows).

Added: I'm also frustrated that when I share my personal experience of the process with Mozilla, people won't have it (not talking about _yoasif here, good work on those successful reports!). I get that it's your baby, that you have a personal relationship with Mozilla that makes you want to defend it, but if you love it, you must allow it to face honest criticism, even if at the end of the day you'll choose to ignore it.

Re:Teaching machines to triage Firefox bugs by fabricexpert on Tuesday April 09, 2019 @05:26PM (#19619093)
Thanks for your service