Re:Ask HN: Firefox vs. Chrome security
by kbenson on Wednesday November 15, 2017 @11:55AM
(#15705218)
> there is no way a developer can write a code in Rust that causes segfaults ( atleast language promises that ).
Well, as long as you avoid unsafe blocks (which turn off a few safety features in a specific scope so you can do complex or performance critical things in that scope) you're supposed to be safe, but to my knowledge it's not formally proven. In practice it seems to be working quite well though.
Re:Ask HN: Firefox vs. Chrome security
by gsnedders on Wednesday November 15, 2017 @11:59AM
(#15705259)
> there is no way a developer can write a code in Rust that causes segfaults ( atleast language promises that ).
Well, you can very easily: write bad code in unsafe blocks.
That said, your badness is contained within unsafe blocks, so hopefully you have much less code to closely review.
Re:Ask HN: Firefox vs. Chrome security
by rammy1234 on Wednesday November 15, 2017 @02:08PM
(#15706782)
right, it is well known to the developers what to look for when we see something wrong. it doesnt crash randomly, it cries out loud when it fails so we know what is happening and manage it better.
recent blog post https://blog.rust-lang.org/2017/11/14/Fearless-Concurrency-I...