2 ms·
Not a TL;DR but if you prefer to read comments skipping the article, here are some juicy bits about supporting a web browser supporting a "fork of Mozilla Fire
by karmakaze 6y ago
Not a TL;DR but if you prefer to read comments skipping the article, here are some juicy bits about supporting a web browser supporting a "fork of Mozilla Firefox for the Power Macintosh and Mac OS X Tiger PowerPC".
> If you aren’t paying for the software, then please don’t be a jerk. There is a human at the other end of those complaints and unless you have a support contract, that person owes you exactly nothing. Whining is exhausting to read and “doesn’t work” reports are unavoidably depressing, disparaging or jokey comments are unkind, and making reports nastier or more insistent doesn’t make your request more important. This is true whether or not your request is reasonable or achievable, but it’s certainly more so when it isn’t.
> As kindly as I can put it, not all bug reports are welcome.
> And that puts undue pressure on the one guy who is pushing this specific platform forward on what is arguably its most important tool. (On top of all of this Kaiser, a medical doctor and infectious diseases expert, [...] during a pandemic, [...] who briefly hinted at this in his TenFourFox post, literally was the person who called off Coachella this year.)
So in addition to maintaining a fork of Firefox he averts an explosion of COVID-19 cases from Coachella in his day job.
- bombcar 6y agoI think it goes beyond “free” software and should be a rule of thumb for any bug reports - be polite, be descriptive, be appreciative and don’t expect anything. It’s rare software where the “customer” whether paying or not has much influence on getting something fixed - your best bet is almost always going to be following the list above.