Several months in the life of Project Zero – Part 1: The Chrome bug of suffering

Re:Several months in the life of Project Zero – Part 1: The ... by xvilka on Wednesday February 12, 2020 @09:25AM (#22309021)

There is no reason to spend time on any variant of C in the age of Rust.

[ Parent | on HN ]

Re:Several months in the life of Project Zero – Part 1: The ... by pjmlp on Wednesday February 12, 2020 @10:05AM (#22309326)

Sure there is, as much as I dislike C, no one is going to port the existing UNIX and POSIX clones to something else.

And even then, many of those interfaces are based in C semantics anyway.

So anything that helps to reduce the amount of possible security exploits per line of C code is welcomed.

[ Parent | on HN ]

Re:Several months in the life of Project Zero – Part 1: The ... by acdha on Wednesday February 12, 2020 @10:25AM (#22309516)

For new projects, sure. For existing projects, it's not trivial to convert them and anyone working on something significant is going to need time to do a migration during which additional new C code will almost certainly need to be written.

[ Parent | on HN ]

Re:Several months in the life of Project Zero – Part 1: The ... by xvilka on Wednesday February 12, 2020 @11:30AM (#22310197)

It can be semi-automated with the amazing c2rust[1] tool.

[1] https://github.com/immunant/c2rust

[ Parent | on HN ]

Re:Several months in the life of Project Zero – Part 1: The ... by acdha on Wednesday February 12, 2020 @12:50PM (#22310922)

“semi-” is not a synonym for “easily done with production-ready results”. Until that changes, people are going to need to write new C code even if they're working to refactor their code into a better language.

[ Parent | on HN ]

Re:Several months in the life of Project Zero – Part 1: The ... by fortran77 on Wednesday February 12, 2020 @10:26AM (#22309524)

Good point. We can do this in Go.

[ Parent | on HN ]