News for hackers. Stuff that matters.
Re:Mitigating Memory Safety Issues in Open Source Software by pyb on Thursday February 18, 2021 @08:12AM (#26179408)
-
Re:Mitigating Memory Safety Issues in Open Source Software by sgift on Thursday February 18, 2021 @08:20AM (#26179473)
Since they don't do that (it's right there in the announcement, which no one in this thread seems to have bothered to read) that whole point is moot:

> The ISRG's approach of working directly with maintainers to support rewriting tools and libraries incrementally falls directly in line with our perspective here at Google.

And a link to: https://www.abetterinternet.org/post/memory-safe-curl/

Re:Mitigating Memory Safety Issues in Open Source Software by chii on Thursday February 18, 2021 @08:19AM (#26179462)
Then be satisfied that your project is a good enough idea that someone else is willing to put up money to rewrite it using a safe language.

But if you're not the one doing the rewrite, why would google pay you? And if you would be capable of such a rewrite, may be they would pay you to do so.

Re:Mitigating Memory Safety Issues in Open Source Software by machello13 on Thursday February 18, 2021 @08:18AM (#26179455)
Wouldn't feel great, but what in the article gave you the idea they're doing that?