>>108777758
Is this the result of AI finding bugs, vibecoding causing bugs, or a combination of both?

>>108777795
Yes

>>108777795
https://hacks.mozilla.org/2026/05/behind-the-scenes-hardening-firefox/

>>108777795
mythos

>>108777795
They never had too many people working on bugs, so they mostly just address critical ones.

>>108777758
i mean, its the convolution of a step function over a uniform medium. or something like that... haven't touched control theory in a while.

sort of like when indigenous people are exposed to eurochads for the first time in their thousand year existence.

you will see an exponential decay curve from this point onward as the codebase absorbs this new pair of eyes.

>>108778015
yeah, that makes sense
I need to take a closer look at this, apparently the bugs should be public
because there's a lot of little shit I notice in a lot of the projects that I've worked on over the years where everyone is aware that there could be an issue, or a vulnerability, or just wonky behavior, but the input is "sanitized" in all paths towards that code (yeah, maybe in the future that won't be the case) in such a way that it is virtually impossible for it to happen and making the code 100% bullet proof would make it needlessly complicated, or unreadable, or slow, or whatever, so we just let it be
if you let a machine go through it, suddenly it finds 100 "bugs" that the stupid humans missed