94 points by speckx about 17 hours ago | 47 comments | View on ycombinator
operation_moose about 17 hours ago |
paulirish about 16 hours ago |
Turns out I personally responded. (Did not expect that)
It was a bug in WebKit that was resolved a year later.
I have no memory of the bankruptcy closures 14yrs ago. He probably has a fair point. But anyway, details there for the curious.
IMO the title should probably have a "(2012)" suffix.
strenholme about 16 hours ago |
The problem with bug reports is that the majority of them are feature requests. Or they are support requests. Very rarely are they actual bug reports.
So, I turned off bug reports.
The way I handled them before the age of bug tickets was to have a mailing list, and to tell people who emailed me privately to instead send an email to the list if they wanted support. This way, the community as a whole could either support the person, or we could have a discussion about why I wasn’t going to implement their favorite pet feature “for fun and for free”.
Right now, in the age of AI-automated attacks based on 0-days, developers need to pause adding new features and make anything Internet-facing as secure as possible (I’m very lucky my little open source project has never had a remote code execution bug).
gavinray about 16 hours ago |
Only once have I taken the time to submit a Chrome bug report.
Chrome Canary updated and then refused to launch entirely, on Windows 11. I dumped the Event Viewer and application crash logs into the bug report.
It was fairly promptly fixed, and an overall positive experience.
- https://issues.chromium.org/issues/465823612
- https://chromium-review.googlesource.com/c/chromium/src/+/72...
bredren about 17 hours ago |
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.
jamie_ca about 17 hours ago |
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 about 17 hours ago |
settsu about 16 hours ago |
cosmotic about 14 hours ago |
hackrmn about 17 hours ago |
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).
ginthian about 15 hours ago |
motbus3 about 16 hours ago |
Wowfunhappy about 17 hours ago |
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?
rikschennink about 17 hours ago |
lulzhipsters about 10 hours ago |
undefined about 16 hours ago |
roncesvalles about 17 hours ago |
coldfloor about 16 hours ago |
Also every large tech company I've ever worked at has done this periodically. Especially when I worked on small teams that built internal tools. We'd have years of bugs and feature requests that we'd never be able to address. Half the open tickets were from people that had left the company. So every few years management would mass-close things with a "If this is still relevant re-open it."
> [ 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.