News for hackers. Stuff that matters.
Re:Mitigating Memory Safety Issues in Open Source Software by bachmeier on Thursday February 18, 2021 @08:59AM (#26179853)
A rewrite is not taking it "to the next level". It provides a new version in a new language that does the same things, and if things go according to plan, will have fewer safety issues. There's nothing that binds them to maintain any of these projects. Given Google's history, it's irresponsible to not consider long-term maintenance and other issues.
Re:Mitigating Memory Safety Issues in Open Source Software by emteycz on Thursday February 18, 2021 @09:23AM (#26180079)
No, C and Rust definitely don't do the same things. If the project is open source, I don't see how any maintenance concerns are relevant - everybody can judge for themselves.
Re:Mitigating Memory Safety Issues in Open Source Software by gordian-mind on Thursday February 18, 2021 @10:53AM (#26181279)
It's not that smart to mistake the purpose or specification of a program, with its implementation.

Anyway, if everybody can judge for themselves, then I guess it's cool to judge that giving Google an inch over many critical open source projects is a horrible idea.

Re:Mitigating Memory Safety Issues in Open Source Software by cycloptic on Thursday February 18, 2021 @02:03PM (#26184034)
You speak as if it's impossible for someone outside Google to maintain a project that isn't written in C++ or C...
Re:Mitigating Memory Safety Issues in Open Source Software by emteycz on Thursday February 18, 2021 @10:58AM (#26181356)
Sure, nobody says you have to use their software. But don't claim that they don't give back or that it's purposeless.