5 ms·
I appreciate the time you spent to make that informative post, and as a professional software developer I also appreciate the value of good bug reports. However
by Silhouette 13y ago
I appreciate the time you spent to make that informative post, and as a professional software developer I also appreciate the value of good bug reports. However, IME this simply isn't true:
People put a huge amount of time into working around, and complaining about, cross browser issues. Devoting a small fraction of that time to submitting regression tests instead would dramatically decrease the number of problems in the future.
The effort required for a regular user to file a bug report in the major browsers is insane. The bug trackers involved are among the most user-hostile and over-complicated interfaces I have ever encountered.
Developers move to six-weekly releases with at least three different flavours in the works at any given time, and then expect people running the regular browser to install a completely different version of the software to test things before filing bug reports. This is insane.
In Firefox's case in particular, users are often asked to create a new profile, which AFAIK still requires command-line hackery and, from direct personal experience, carries a significant risk of corrupting or destroying your regular profile even if you follow the instructions to the letter. This is insane.
And even if users do make the Herculean effort required to create a minimal test case, install the latest development versions of the browser, create a clean profile if necessary, confirm that the bug still happens, and fight through the bug tracker to file a report, there is still no guarantee that anything will actually be done about it. Quality of implementation is obviously not the priority for several of the major browser developers, certainly not Mozilla and Google, and major bugs and site-breaking regressions are frequently ignored for very long periods while shiny new features no-one is actually going to use in production for years and another 0.3642% performance boost in JavaScript are prioritised.
As I said, I'm a professional software developer, and as such I appreciate the value of good bug reports and feedback from users, and I hate it when users make blanket criticisms. But Mozilla and Google are among the most user-hostile organisations on the software landscape in this respect, and until they fundamentally change their approach, I don't see this situation improving. Meanwhile, their users, and those of us trying to develop web sites and applications to support those users against a constantly moving and frequently breaking target, are the ones who lose out.
For the record, I debated whether to post this. Ranting on public forums is rarely constructive. But in this case, I think the presumption that it takes much less time to file good bug reports than to find workarounds must be challenged, or the situation isn't going to improve. For someone who isn't a regular contributor, following the guidelines to file a bug report in the way that Mozilla and co would like isn't the five minute job it should be, it's closer to a five hour job, and I think sometimes the developers/regular contributors/bleeding edge alpha testers don't even realise that.
- daleharvey 13y ago> As I said, I'm a professional software developer, and as such I appreciate the value of good bug reports and feedback from users, and I hate it when users make blanket criticisms. But Mozilla and Google are among the most user-hostile organisations on the software landscape in this respect, and until they fundamentally change their approach, I don't see this situation improving. This seems like a strange comment What other large scale software do you use on a day to day basis that you can even find and report bugs instead of just sending them in to some companies /dev/null and hope they eventually get fixed
- Silhouette 13y agoIt's not only the difficulty in reporting bugs that is the problem, it's the rapid release cycle and the frequent regressions and bugs it seems to introduce. I don't know which of the other "large scale software" I use would have the same difficulty reporting bugs, because nothing else I use breaks basic functionality every few weeks. However, for smaller-scale things, I've recently been in touch with a couple of on-line services I use and the manufacturer of a hardware device I bought about various problems. I interacted one-to-one or even one-to-many with some of their technical folks, with very satisfactory service in each case. No doubt there is a bug tracker somewhere on the other side and some new records got created in it along the way, but all I had to do was send a simple message describing my problem and then answer their rapidly-provided follow-up questions. I was happy to make the effort to do that, because they made it easy for me to help and gave me a feeling that my effort was doing something useful. I would be just as happy to contribute usefully to supporting browsers if it was just as easy to do it. I want to help, and for a long time I really tried to do so. But I live in the real world, and I literally can't afford to spend half a day when no client is paying me just to do someone else's testing for them every time I find a bug in a major browser. Once in a while I could cope with, in the spirit of helping out. Several times a month just isn't practical.
- ohkine 13y agoI agree with you. I work in software development and have followed Mozilla's bug tracker for over 5 years, and i STILL don't really understand how to use Bugzilla. On the dozen or two occasions that i've filed a ticket, probably 1/3 of them ended up being duplicates (which i always search for, but never find, because i don't get how to use Bugzilla's search function), and another 1/3 end up going un-acknowledged. The remaining 1/3 get acknowledged, but i've yet to see one actually get fixed (which i understand is a function of resources and blah blah, i'm not bitter about it or anything). On one occasion, i was able to locate the source of the bug i had, and, even though i had absolutely zero experience with 'lower-level' languages like C++ at the time, i decided i would fix it. I pulled trunk and managed to build it, which was an enormous affair, let me tell you, and in the end i had a fix. I submitted the patch, but was told that i would need to put it through their testing system. I was given a link to a wiki, but this entire process was just absolutely beyond me at the time and i bailed on it. I just wanted to help them fix a bug. The bug is still there to this day. To Mozilla's credit, they did (do?) have a user-feedback extension with the beta/Aurora builds that allows regular users to report bugs in a simple manner directly from the browser. You'd pick 'Firefox made me sad' and then just type what the problem was and click submit. However, i have no idea where these bugs go, how closely they're looked at, or how successful they've been in reducing bugs.