3 ms·
Yes but why do it in C++? There is no compiler enforced safe mode and you're by definition implementing an engine to run hostile code in it.
by hawk_ 1y ago
Yes but why do it in C++? There is no compiler enforced safe mode and you're by definition implementing an engine to run hostile code in it.
- monax 1y ago> There is no compiler enforced safe mode It's still early days, but Clang can check some lifetimes, using the [[clang::lifetimebound]] attribute [1]. You can also restrict unsafe pointer usage [2] outside designated blocks of code—somewhat like Rust’s unsafe keyword. [1] https://clang.llvm.org/docs/AttributeReference.html#id8 https://clang.llvm.org/docs/AttributeReference.html#id8 [2] https://clang.llvm.org/docs/SafeBuffers.html#buffer-operations-should-never-be-performed-over-raw-pointers https://clang.llvm.org/docs/SafeBuffers.html#buffer-operatio...
- userbinator 1y agoI personally have had enough of the "security" bullshit after seeing what it's done to "secure" control over the population and put that in the hands of the enemy.
- saagarjha 1y agoI thought you were happy that your man was finally fixing things this year.
- userbinator 1y agoYou of all people should know better than to bring that crap here, but guess how the Rust crowd leans politically.
- saagarjha 1y agoI think if you're going to bring up how security has a political angle to it (repeatedly!) you should not be surprised if people remember the arguments you recycle for the topic
- npalli 1y agoSince 2012, all future browsers will be written in Rust and looks like it will always be that case. Perhaps, programming a browser in Rust is a painful activity that nobody seems to have managed to complete (writing parts of it since the Servo days). Talking about safety though, nonstop, yeah no shortage of that.
- School-Cotton 1y agoFWIW nobody has written a new complete browser engine in any language since then, not just Rust.