Experimenting with Rust in Chromium
chromium.googlesource.com
Experimenting with Rust in Chromium
1–10 of 115 posts
Re: Experimenting with Rust in Chromium
#2It was bound to happen eventually. Big projects like Chromium tend to move slowly so it will probably be a few years before any Rust code ends up in a shipped release. But this is a great start!
Re: Experimenting with Rust in Chromium
#3It was bound to happen eventually. Big projects like Chromium tend to move slowly so it will probably be a few years before any Rust code ends up in a shipped release. But this is a great start!
I don’t think Chrome is moving slowly. They are on the very edge of web technology. They are for example relatively fast at adopting modern C++ standards (compared to other big code bases). [1]
[1] https://chromium.googlesource.com/chromium/src/+/HEAD/styleg...
Re: Experimenting with Rust in Chromium
#4[deleted]
Re: Experimenting with Rust in Chromium
#5It was bound to happen eventually. Big projects like Chromium tend to move slowly so it will probably be a few years before any Rust code ends up in a shipped release. But this is a great start!
Chrome is indeed big, however calling them slow is incorrect.
In fact there are articles of people burning out with the release process of Chrome, left behind by the sheer speed at which the project is moving forward.
Re: Experimenting with Rust in Chromium
#6It was bound to happen eventually. Big projects like Chromium tend to move slowly so it will probably be a few years before any Rust code ends up in a shipped release. But this is a great start!
Chrome is indeed big, however calling them slow is incorrect. In fact there are articles of people burning out with the release process of Chrome, left behind by the sheer speed at which the project is moving forward.
Can you give examples for the articles? Very interested in knowing
Re: Experimenting with Rust in Chromium
#7Even though it'd be a while before this really affects the Chrome codebase, it's a real testament to how well Rust nails the safe-but-low-level niche. Google does not lack resources to tool (or staff!) a C++ codebase correctly, nor does it lack resources to build languages[1] targeting these specific problems; that they'd consider Rust isn't just because "it's there".
Re: Experimenting with Rust in Chromium
#8It was bound to happen eventually. Big projects like Chromium tend to move slowly so it will probably be a few years before any Rust code ends up in a shipped release. But this is a great start!
Chrome is indeed big, however calling them slow is incorrect. In fact there are articles of people burning out with the release process of Chrome, left behind by the sheer speed at which the project is moving forward.
This is so true. There were tens of Chromium based browsers which had a good niche market interests but eventually failed to keep up with Chromium's super fast development pace. I'm pretty sure that the Edge team spends lots of their eng time solely on rebasing and one of the key factor for a successful Chromium based-browser project is to manage clean separation of your domain code and Chromium codebase. Otherwise, your team member will be quickly burnt out and leave the team.
Re: Experimenting with Rust in Chromium
#9It was bound to happen eventually. Big projects like Chromium tend to move slowly so it will probably be a few years before any Rust code ends up in a shipped release. But this is a great start!
Chrome is indeed big, however calling them slow is incorrect. In fact there are articles of people burning out with the release process of Chrome, left behind by the sheer speed at which the project is moving forward.
You're right. I meant to say big projects tend to be conservative with adopting new technologies. I didn't mean to imply anything about development pace.
Re: Experimenting with Rust in Chromium
#10Even though it'd be a while before this really affects the Chrome codebase, it's a real testament to how well Rust nails the safe-but-low-level niche. Google does not lack resources to tool (or staff!) a C++ codebase correctly, nor does it lack resources to build languages[1] targeting these specific problems; that they'd consider Rust isn't just because "it's there". [1] https://github.com/google/wuffs
Story time.
I worked at Google years ago and there was a presentation once done on some optimizations done on Chrome performance. This is probably 10 years ago now.
So C++ has std::string of course. C libraries however use "const char ", which has lots of problems. The C++ designers allowed you to avoid friction here by allowing you to pass a std::string to a function expending a const char . Technically, this is an operator method.
It was discovered that the Omnibar in Chrome went through many layers of translations between std::string and const char *, back and forth, such that there were approximately 25,000 string copies per keypress in the Omnibar.
So my point is that even with a ton of resources writing good, efficient and performant C++ is still nontrivial. And that's really the point of Rust (well, one of them).