I'm confused. Is this something that just happened or was it 2012 and the story was just posted yesterday for some reason?
> [ I wrote this in August 2012 and then forgot about it. ]
Edit: I think it is old based on the addenda
> A Mastodon colleague was complaining today about a similar practice, and I wanted to refer him to this article, but couldn't because I had completely forgotten to publish it.
Fair enough I guess, but odd choice to start the article with "18 months ago" and date it 18/11/2026.
Great argument to pay $ for open source software. Both parties are incentivized to submit and respond to high quality bug reports.
The Google open source model is an unfortunate one. The rest of the world is forced to compete with "funded by ad money" or to give their work away for free (Firefox, Ladybird, etc.).
Imagine anyone who uses a web browser paid $1 for a yearly license? $10B/year to fund a software company that develops it? The dream.
Vote with my feet and go where? Apple Feedback reports are an infamous black hole, so not Safari. Firefox has had some bugs stay open for 15 years or more. And everything else is reskinned Chrome.
The author even linked to the jwz CADT article about how this attitude is endemic to open source (and nothing has improved in the >20 years since he posted it). There’s nowhere to go that’s any better.
...this really would be the perfect use case for AI, wouldn't it?
Of course actual code changes to something like Chromium need to be driven by humans, for all sorts of reasons. And I'm not suggesting Google should hand over all bug triage to a machine, or anything like that.
But if you've already decided, for better or worse, that you're going to auto-close old issues—maybe at least have an AI look at them first? The bug was clear and straightforward; an agent should be able to confirm that it still exists, either by reproducing it or by looking at code changes since the problem was reported. It doesn't even need to be a particularly strong model. Surely Google of all companies has the compute for that?
> it came up as a "broken image" icon (which isn't a bug) and failed to display the alt text from the img tag (which is)
The test page he provided http://perl.plover.com/NPC/test.html renders correctly for me in Chrome on Mac (Firefox renders the alt text, but no broken image icons), maybe the bug report _is_ obsolete?
> [ I wrote this in August 2012 and then forgot about it. ]
Edit: I think it is old based on the addenda
> A Mastodon colleague was complaining today about a similar practice, and I wanted to refer him to this article, but couldn't because I had completely forgotten to publish it.
Fair enough I guess, but odd choice to start the article with "18 months ago" and date it 18/11/2026.
A genuine bug report is a professional contribution. These are commercial enterprises.
They should be paying people for reports in appreciation at least.
Vote with your feet.
The Google open source model is an unfortunate one. The rest of the world is forced to compete with "funded by ad money" or to give their work away for free (Firefox, Ladybird, etc.).
Imagine anyone who uses a web browser paid $1 for a yearly license? $10B/year to fund a software company that develops it? The dream.
The author even linked to the jwz CADT article about how this attitude is endemic to open source (and nothing has improved in the >20 years since he posted it). There’s nowhere to go that’s any better.
Of course actual code changes to something like Chromium need to be driven by humans, for all sorts of reasons. And I'm not suggesting Google should hand over all bug triage to a machine, or anything like that.
But if you've already decided, for better or worse, that you're going to auto-close old issues—maybe at least have an AI look at them first? The bug was clear and straightforward; an agent should be able to confirm that it still exists, either by reproducing it or by looking at code changes since the problem was reported. It doesn't even need to be a particularly strong model. Surely Google of all companies has the compute for that?
The test page he provided http://perl.plover.com/NPC/test.html renders correctly for me in Chrome on Mac (Firefox renders the alt text, but no broken image icons), maybe the bug report _is_ obsolete?