Google Chrome dev team declares bug report bankruptcy

(blog.plover.com)

41 points | by speckx 35 minutes ago

8 comments

  • operation_moose 21 minutes ago
    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.

  • bredren 28 minutes ago
    Any large commercial organization wants people to fill out surveys or give feedback on their new app or their call center person.

    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.

    • nsoam 19 minutes ago
      Paying people for bug reports is how you get your bug tracker inundated with invalid reports from Indians.
    • levkk 11 minutes ago
      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.

    • Analemma_ 23 minutes ago
      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.

  • jamie_ca 22 minutes ago
    > 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?

  • theragra 15 minutes ago
    I remember how I submitted bug in Gmail. I've checked it 6 years later, and it still was there.
  • hackrmn 2 minutes ago
    I work at a place where if you have too many "open tickets", you get a message from someone in a managerial position telling you that you have too many open tickets ("thanks, I did not know that!"). The kicker is, however, our ticket assignment works on a best-fit basis, and I dip my hands in enough stuff a lot of cases are assigned to me, and I don't mind. What I do mind though, is having to close tickets just to close tickets to fill someone else's absurd and abstract and useless bottom-line. But the managers don't seem to understand the difference between closing tickets and helping people. I don't close tickets before the case is resolved, and I don't care that there is a ticket assigned to me five years ago about a GPU virtualisation problem that may have gone stale 2 years back when NVIDIA, bless their heart, updated their drivers. I can't attend to the ticket on a whim, and it's on a long back-log, but I _know_ the problem may still be there which is why I keep the ticket assigned to myself. And so on.

    I am pretty sure Google has the same problem as I attribute to our work place (just to be clear, no I do not have a problem with too many tickets, we're storing garbage 100x the volume these tickets require as upkeep, and in a year it will be 100x more for the former).

  • rikschennink 3 minutes ago
    In the analogy the neighbor is also a billionaire, making the interaction even worse.
  • Wowfunhappy 7 minutes ago
    ...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?

  • roncesvalles 4 minutes ago
    [dead]