Earlier quoted context omitted.
Exactly, also it lacks a lot of context as to why they did that. Possible (probable?) scenario: - Marketing: "we found and fixed lots of bugs thanks to AI" - Reality: the KPI is now to fix as many bugs as possible with the help of AI, so they used AI to search old and easy bugs in the backlog, and then fixed it manually
Huh? Maybe a third scenario is that AI helped fix the bugs? Like described in the actual post you are replying to? This level of conspiracy theory is getting a bit ridiculous.
Google fixed more Chrome bugs in June than over the past two years, thanks to AI
531–540 of 668 posts
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#532Earlier quoted context omitted.
> 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…
Ekhem. When Chrome was announced there wasnt Rust. And Java was a programming language for slow moving systems, with many a flaws and its own classes of footguns. 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
#533Earlier quoted context omitted.
Well we make work with the tools we have It worked well enough, maybe "fit for purpose" is a stronger word
Makes sense, but strangely, no one has responded to my question about why Servo hasn't been picked up, if Rust is such an important factor in browser engine implementation. People are calling using C and C++ "ridiculous" and "irresponsible" and "not fit for purpose". And yet, no one's using the alternative that's sitting right there?
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#534Earlier quoted context omitted.
And how many were introduced by AI?
It's the opposite: humans. The most critical one (sandbox escape) has been sitting there for 13 years.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#535Earlier quoted context omitted.
You make a false equivalence between being an idiot/“didn’t know what they were doing” and not knowing how to properly manage memory. Also, why do you think the devs who worked on google chrome weren’t idiots? Some of the most important and safety critical large scale projects in the history of humanity had/have manual memory management. If you think the effort of doing it correctly is not worth it for certain projec…
if you go around pulling out logic flaw arguments and then proceed to commit logic flaws yourself, it isn't a good look man. the quoted statement was "beyond most intelligent individuals" which contradicts your assertion that the argument was stated as "humans cannot write correct C". anyway I do find it ultra amusing how software engineers believe software engineering is the backbone of programming, when in reality…
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#536Earlier quoted context omitted.
Why is everyone always referring to logic errors when pushing back against Rust? No programming language ever invented (or to be invented) will fix logic errors made by developers . Logic errors are "out of scope" for Rust or any other programming language.
The Rust type system helps you catch logic errors at compile time. Same with Haskell or Ocaml.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#537Earlier quoted context omitted.
What software would that be, and how do you know there have never been memory-related bugs and vulnerabilities in it?
Basically all C programs I use, shells, editors, terminals, etc. But I do not claim that there "never has been a memory-related bug" but that it is not "riddled with" memory-related bugs, which I would expect would have manifested in at least one segfault over all these years, which I did not observe.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#538Earlier quoted context omitted.
I'll await your Rust ports of Windows, Linux and MacOS then. This isn't really a fair take. Keep in mind that C/C++ has been the backbone of the most important software in the world since the 1970s. At that time we didn't have virtually unlimited compute and memory at our fingertips the way we do now. It was a huge improvement to have a high level language which still could be optimized nearly as well as assembly. It…
> I'll await your Rust ports of Windows, Linux and MacOS then. Unironically this. Like most game developers, I was extremely sceptical of Rust, based on opinions I've read on the internet. Ugliest syntax I've ever seen, and "safety" features are irrelevant and just get in my way. Compile times are glacial. Tons of direct and indirect dependencies needed. But then I got to use it professionally for a year or so, and I…
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#539Earlier quoted context omitted.
if you go around pulling out logic flaw arguments and then proceed to commit logic flaws yourself, it isn't a good look man. the quoted statement was "beyond most intelligent individuals" which contradicts your assertion that the argument was stated as "humans cannot write correct C". anyway I do find it ultra amusing how software engineers believe software engineering is the backbone of programming, when in reality…
[flagged]
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#540The real datapoint was Firefox not paying any money in Berlin's Pwn2Own competition round this May just gone. Unheard of to have nothing confirmed... they've paid out every event since 2007 (I checked). Does this mean we must move past the low-hanging fruit now? Probably... Certainly indicates some usefulness of these models.
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