To me this merely signals how broken C++ development really is. Most if not all of the bugs being uncovered are memory related and therefore intimately tied to the mental memory model of C and C++, namely manual memory management. It's fine for a C or C++ program encompassing a couple hundred lines but beyond that it's a liability. C and C++ are simply not fit for purpose when large scale software projects are concer…
Google fixed more Chrome bugs in June than over the past two years, thanks to AI
441–450 of 668 posts
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#442To me this merely signals how broken C++ development really is. Most if not all of the bugs being uncovered are memory related and therefore intimately tied to the mental memory model of C and C++, namely manual memory management. It's fine for a C or C++ program encompassing a couple hundred lines but beyond that it's a liability. C and C++ are simply not fit for purpose when large scale software projects are concer…
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#443Earlier quoted context omitted.
The entire compute world was built on top of C and C++. Saying they're not fit for purpose doesn't seem correct. I think what you're really saying is they're not an optimal choice from a safety perspective. > All of these need to be ported to Rust or another memory-safe language ASAP to prevent mayhem. Seems like hyperbole... It might be ideal if we could snap our fingers and suddenly have rust ports, but I feel like…
> Saying they're not fit for purpose doesn't seem correct. I'll quite happily say they were never fit for purpose. C had a role in bootstrapping early software development in the absence of anything better but once Lisp, Delphi, Smalltalk and Java arrived on the scene then it, and its equally footgunnable variants, should have been pushed to the margins where hardware constraint was the primary consideration. Writing…
I dont think they had much of a choice in 2008. Now? Sure. I bet a rust port is in the works.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#444Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#445Earlier quoted context omitted.
Perhaps this was due to their red-teaming partnership [1][2] with Anthropic which they wrote about a few months earlier in March? 1: https://www.anthropic.com/news/mozilla-firefox-security 2: https://blog.mozilla.org/en/firefox/hardening-firefox-anthro... Previous discussion: https://news.ycombinator.com/item?id=47273854
I just did a search and apparently this fact (the specific one about no payouts for the first time in almost 20 years) has not gotten a discussion on HN. Given the degree of skepticism around the utility of AI bug finding and fixing (this very thread is full of it), I would have thought that concrete evidence that it can help actually make real software more secure against attacks would have gotten a write-up somewhe…
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#446Google Home became so unbelievably buggy, and I felt so betrayed by that, that I stopped using every single Google product - from Gmail to Android to Google Cloud Platform. The few physical Google devices that I'm yet to replace account for 10% of my tech, but still cause 90% of my problems.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#447How many of those automated fixes were reverted? How many introduced a new bug? What's the false positive rate on the finding agents? The post has counts for everything that went right and nothing for what could go wrong.
> The post has counts for everything that went right and nothing for what could go wrong. That's AI for you. At Amazon we have many forums to share our AI wins, but none to share AI failures or disappoinments. No wonder execs make bad decisions regarding AI, they only hear completely one-sided stories.
I come to HN to read about AI failures and disappointments.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#448Earlier quoted context omitted.
Not sure what materials your hoping for, but I've pointed codex at pprof application endpoints and just told it to identify hotspots and propose lowest hanging fruit/highest ROI items to fix, which I then approved it to open PRs for. Reduced application CPU usage by ~30% on loaded servers. It's not magic. Fairly obvious oversights that I or someone else on the team could've found and fixed if we had looked, but it wa…
Ideally a blog post on an open source project that shows harness, model, prompt and the before/after measurements plus the PR.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#449Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#450Earlier quoted context omitted.
[flagged]
You think they're talking about giving them access to a live prod db/app? You know offline copies are a thing right?