3 ms·

Type / memory safety != security. The Rust people also mistake "no segmentation faults" for "no crashes".

• kibwen 12y ago
  > The Rust people also mistake "no segmentation faults" > for "no crashes". I was a witness to one of the first public demonstrations of Servo to the Mozilla community at large (Mozilla Summit 2013). At one point during the demonstration Servo suffered a runtime panic, and the presenter (a Servo dev) self-deprecatingly apologized for the crash. A Gecko engineer in the audience raised his hand and asked if it was a segfault. The answer was that it was not, to which the Gecko engineer replied, "well then it's not actually a crash". So yes, now we're arguing semantics, but in a systems programming context a segfault is most usually what one means by "crash".
• pcwalton 12y ago
  > Type / memory safety != security Type and memory safety certainly does enhance security, by eliminating classes of vulnerabilities. Security isn't a binary thing. > The Rust people also mistake "no segmentation faults" for "no crashes". To a systems programmer the meaning of "no crashes" is pretty clear. A Web page (or your browser) doesn't crash because the JavaScript on the page threw an unhandled exception. Rust panics work like exceptions.