Comment by rvz
2 days ago
> We will improve our static analysis and testing practices to correctly handle errors and if need be fail open.
> Without the appropriate error handling, the null pointer caused the binary to crash.
Even worse if this was AI generated C or C++ code, wasn't this not tested before deployment?
This is why you write tests before the acutal code and why vibe-coding is a scam as well. This would also never have happened if it was in Rust.
I expect far better than this from Google and we are still dealing with null pointer crashes to this day.
I'm as much of a Rust advocate as anyone, but what does vibe-coding have to do with any of this?
Seems to just be the new thing to casually hate on.
"If this was vibe coded, this is even worse. This proves that vibe coding is bad."