Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Chromium Chrome Google Open Source

Google To Allow Rust Code In the Chromium Browser (phoronix.com) 23

Google announced today that moving forward they will be allowing Rust code into the Chromium code-base, the open-source project that ultimately served as the basis for their Chrome web browser. Phoronix reports: Google is working to introduce a production Rust toolchain into their build system for Chromium and will be allowing Rust libraries for use within Chrome/Chromium. The timeframe for getting this all together is expected within the next year following a slow ramp. Google is backing Rust for Chromium to allow for simpler and safer code than "complex C++" overall, particularly around avoiding memory safety bugs. In turn using Rust should help speed-up development and improve overall security of the Chrome web browser. Initially they are focused on supporting interop in a single direction from C++ to Rust and for now will only be supporting third-party libraries for their Rust usage.
This discussion has been archived. No new comments can be posted.

Google To Allow Rust Code In the Chromium Browser

Comments Filter:
  • In turn using Rust should help speed-up development and improve overall security of the Chrome web browser.

    I accept the idea that there will be fewer memory bugs, but if they are able to speed up development, they are doing something seriously wrong with their C++ development.

    • But just the same, this makes sense more so than the Linux kernel push right about now? Letting people see something work?

    • I strongly disagree with that, finding bugs takes more time than writing the code in the first place to begin with but even apart from that, C++ code is far more verbose.

      The real issue is of course that C++ has far wider architecture support than Rust.

    • by gweihir ( 88907 )

      Indeed. Also, they will just get bugs in other places, probably as bad but harder to find in testing. Memory bugs are a symptom of incompetent developers and these will always find ways to mess up and will just focus their incompetence on something else now. Apparently there have been some pretty bad security problems with Rust already, at least measured against the minuscule use in actual development.

      • by vyvepe ( 809573 )

        Apparently there have been some pretty bad security problems with Rust already, at least measured against the minuscule use in actual development.

        Any reference for that? I would like to move to Rust from C++. It want to learn what I need to be careful about.

        • by gweihir ( 88907 )

          Go away asshole.

          • You’re going to miss it when it’s gone.

          • by bjwest ( 14070 )
            You have a problem with people who ask for references rather than take some random internet user's word for something?
            • by gweihir ( 88907 )

              You have a problem recognizing an obvious troll?

              • by vyvepe ( 809573 )
                I'm not a troll. You indicated you have a knowledge of "serious security problems with Rust". That surprised me since almost every article I read indicated it is safer than C++. Therefore I wanted to learn more about Rust's security problems. You assumed bad intentions and attacked me in a way which turned out to be quite funny actually.
    • people proficient at C++ are dying off, and Rust is the new black? Because when I read "speed-up development" i understand "throw more resources at it"
  • by jjaa ( 2041170 )
    funny, given that Rust is the brainchild of Mozilla ðY
    • by bjwest ( 14070 )
      Ninety percent of Mozilla's funding comes from web search providers, and I'm guessing a major portion of that is from Google. It wouldn't surprise me one bit to find out Google has quite a bit of influence on Rust development.
    • nicely spoted :D
  • Rust is a replacement for C++, not C.

"The vast majority of successful major crimes against property are perpetrated by individuals abusing positions of trust." -- Lawrence Dalzell

Working...