Windows_Security
Level 24
Thread author
Verified
Honorary Member
Top Poster
Content Creator
Well-known
- Mar 13, 2016
- 1,298
C and C++ like programming language don't have memory integrity enforcement. Although newer compilers offer improvements to check and find memory overflow issues in the code, this basic weakness of C/C++ is the source of all evll (vulnabilities which can be exploited).
In stead of trying to outrun (or better recover ground) Google, Mozilla decided to solve this (memory integrity) problem at its root cause and use a better/safer programming language called RUST.
As far as I know (so feel free to correct) Firefox 48 had the first rust coded module and next version 56 will have another component wriiten in Rust . Firefox 53 used the frst improvements of the new web-engine (which is also written in Rust).
I have not found a fancy progress chart which visualized the lines of code or percentage written in RUST. Being a Firefox critic in the past, Rust might convert me into a Firefox fan in the future. Do any of you know where the progress and conversion can be followed/tracked?
In stead of trying to outrun (or better recover ground) Google, Mozilla decided to solve this (memory integrity) problem at its root cause and use a better/safer programming language called RUST.
As far as I know (so feel free to correct) Firefox 48 had the first rust coded module and next version 56 will have another component wriiten in Rust . Firefox 53 used the frst improvements of the new web-engine (which is also written in Rust).
I have not found a fancy progress chart which visualized the lines of code or percentage written in RUST. Being a Firefox critic in the past, Rust might convert me into a Firefox fan in the future. Do any of you know where the progress and conversion can be followed/tracked?