[HN Gopher] Supporting the Use of Rust in the Chromium Project
___________________________________________________________________
Supporting the Use of Rust in the Chromium Project
Author : mfiguiere
Score : 85 points
Date : 2023-01-12 21:00 UTC (2 hours ago)
(HTM) web link (security.googleblog.com)
(TXT) w3m dump (security.googleblog.com)
| hkalbasi wrote:
| [dead]
| KyeRussell wrote:
| At this point I just internally assume that 'general purpose'
| C/C++ codebases that aren't at least open to the idea of Rust are
| the "if your code has memory issues, you're just an idiot, except
| for the times that my code has had memory issues" types of C
| developers.
|
| More browser code being written in a language with fewer footguns
| is always cause for celebration
| [deleted]
| maccard wrote:
| C and C++ codebases are two very different things.
|
| I work on a large c++ project, and our compile times are awful.
| From my limited experience, moving to rust would absolutely
| ruin our compile times.
| cschep wrote:
| I know rust compile times aren't great but.. are they WORSE
| than C++?? yeesh.
| sli wrote:
| There are a few things you can do to help it. The Bevy
| project has a section of their setup documentation that
| lists a few strategies[0]. In general though it can be
| relatively pretty slow.
|
| [0]: https://bevyengine.org/learn/book/getting-
| started/setup/#ena...
| aliqot wrote:
| In my experience, yes.
| maccard wrote:
| Yeah, they are. The compile times on the toy rust projects
| I've worked on are in the same region of my work c++
| projects.
| aliqot wrote:
| Go compiles near instantly, having used Rust and Go for some
| time now, and shipped in both, Go is the clear winner if you
| value being able to iterate quickly.
| ognarb wrote:
| Please don't put C and C++ in the same boat. This are two
| different languages and while C++ is definitely far from
| perfect, at least there is a lot of contruct to manage memory
| in a safer way (smart pointers raii) and usage of void pointers
| and c-like arrays are heavily discouraged.
|
| Obliviously if you can use Rust, it's even better but that's
| not always the case.
| tptacek wrote:
| Empirically, if they're not the same boat, they're very
| similar boats. People made impassioned arguments for the
| plausibility of memory-safe C, too --- in fact, they still
| do. But look where the bugs come from, and there's a clear
| pattern.
| [deleted]
| AceJohnny2 wrote:
| Considering how Rust started as a way for Mozilla to make the
| Firefox browser more robust, it's kind of fun to see this sort of
| closing of the loop.
| tester756 wrote:
| It shows how good their tech is that even their "competition"
| wants to get it
| [deleted]
| AdmiralAsshat wrote:
| > Rust was developed by Mozilla specifically for use in writing a
| browser, so it's very fitting that Chromium would finally begin
| to rely on this technology too. Thank you Mozilla for your huge
| contribution to the systems software industry. Rust has been an
| incredible proof that we should be able to expect a language to
| provide safety while also being performant.
|
| Somewhere, the laid-off Mozilla Servo team just took a swig from
| their hip flask.
| jackmott42 wrote:
| They might be at Google now.
| azakai wrote:
| Some in fact are.
| bfrog wrote:
| It's just amazing how industrious and creative a small group at
| Mozilla was in order to boot strap Rust.
|
| Cheers to Graydon and Mozilla. Let an elevator never fail you
| again.
| [deleted]
___________________________________________________________________
(page generated 2023-01-12 23:00 UTC)