Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
News
Technology News
Secure by Design: Google’s Perspective on Memory Safety
Message
<blockquote data-quote="ForgottenSeer 107474" data-source="post: 1078236"><p>Interoperability wil increase the ease of transition gigantically, allowing smaller incremental steps of replacing C++ by Rust. In stead of converting large chunks of code which leave the system in a consistent state after completing, interoperability allows for smaller pieces of code with autonomous functions. Because of multi-threading and parallelization of tasks this makes the conversion a lot easier to plan en perform.</p><p></p><p>In layman terms, you can compare this with Formula1 car tire change. Without interoperability a large chunk of code has to be replaced compared with F1-car stopping with old tires and starting again with new tires (you need all the four tires to be able to drive again, so a car with three wheels replaced is not in a consistent state). With interoperability you can replace chunks of code related to the mechanics working at the tire change all at the same time, e.g. first replace the C++ code with Rust for the man holding the stop/go sign (that is an autonomous task), than the mechanic at the front lifting the car with a jack, than the guy unbolting and bolting the wheels, then the guy taking of the old tire, etc. Interoperability allows the mechanic which (un)bolts the tire in Rust can work together with the two mechanics taking of and putting on the new tire who are still working in C++</p><p></p><p>Brave already has put chunks of code (e.g. the build-in adblocker) in Rust. Firefox was the first (both as innovator and driving force) to change C++ to Rust (<a href="https://docs.google.com/spreadsheets/d/1flUGg6Ut4bjtyWdyH_9emD9EAN01ljTAVft2S4Dq620/edit#gid=885787479" target="_blank">link</a>), but they had to cut resources (<a href="https://www.zdnet.com/article/programming-language-rust-mozilla-job-cuts-have-hit-us-badly-but-heres-how-well-survive/" target="_blank">link</a>) because of losing users (Edge taking over Firefox as number two browser). It now seems that Google has stepped in. It must feel to Firefox as a Tapir being slowly strangled by the Anaconda Google. Google might also counteract Brave and Firefox (as possible alternatives after implementing Mv3) by (one) allowing more functionality in Mv3 for adblockers and (two) jumping on the Rust train to memory integrity.</p><p></p><p>Apologize for being a bit skeptical on Google's motives, I am surely applauding their donation to the Rust foundation</p></blockquote><p></p>
[QUOTE="ForgottenSeer 107474, post: 1078236"] Interoperability wil increase the ease of transition gigantically, allowing smaller incremental steps of replacing C++ by Rust. In stead of converting large chunks of code which leave the system in a consistent state after completing, interoperability allows for smaller pieces of code with autonomous functions. Because of multi-threading and parallelization of tasks this makes the conversion a lot easier to plan en perform. In layman terms, you can compare this with Formula1 car tire change. Without interoperability a large chunk of code has to be replaced compared with F1-car stopping with old tires and starting again with new tires (you need all the four tires to be able to drive again, so a car with three wheels replaced is not in a consistent state). With interoperability you can replace chunks of code related to the mechanics working at the tire change all at the same time, e.g. first replace the C++ code with Rust for the man holding the stop/go sign (that is an autonomous task), than the mechanic at the front lifting the car with a jack, than the guy unbolting and bolting the wheels, then the guy taking of the old tire, etc. Interoperability allows the mechanic which (un)bolts the tire in Rust can work together with the two mechanics taking of and putting on the new tire who are still working in C++ Brave already has put chunks of code (e.g. the build-in adblocker) in Rust. Firefox was the first (both as innovator and driving force) to change C++ to Rust ([URL='https://docs.google.com/spreadsheets/d/1flUGg6Ut4bjtyWdyH_9emD9EAN01ljTAVft2S4Dq620/edit#gid=885787479']link[/URL]), but they had to cut resources ([URL='https://www.zdnet.com/article/programming-language-rust-mozilla-job-cuts-have-hit-us-badly-but-heres-how-well-survive/']link[/URL]) because of losing users (Edge taking over Firefox as number two browser). It now seems that Google has stepped in. It must feel to Firefox as a Tapir being slowly strangled by the Anaconda Google. Google might also counteract Brave and Firefox (as possible alternatives after implementing Mv3) by (one) allowing more functionality in Mv3 for adblockers and (two) jumping on the Rust train to memory integrity. Apologize for being a bit skeptical on Google's motives, I am surely applauding their donation to the Rust foundation [/QUOTE]
Insert quotes…
Verification
Post reply
Top
