3 ms·

I wonder how Rust will influence the outcome of this project? Will the Rust paradigm prevent memory leaks or somehow improve on the architecture of the big hitt

I wonder how Rust will influence the outcome of this project? Will the Rust paradigm prevent memory leaks or somehow improve on the architecture of the big hitter browsers like Firefox and Chrome? It's super exciting to see how Rust will fare with building new iterations of existing tech.

steveklabnik 6y ago
Rust doesn’t prevent leaks, by the way, though it doesn’t tend to produce them.
- Filligree 6y ago
  Rust forces you to think about ownership. It doesn't prevent leaks, but it does put you in the right frame of mind to not write them.
untog 6y ago
One thing that interests me about using Rust for a project like this is modularity. The Rust toolchain makes it so easy to work with separate crates that it feels very natural to split your work at logical points. C++ doesn’t have that kind of baked in toolchain and just the act of downloading and compiling the Chromium code is a pretty intimidating prospect. If I could easily download and test, say, a CSS parsing module that could be really useful outside of regular browser contexts.
rumanator 6y ago
> I wonder how Rust will influence the outcome of this project? Currently the project fails to build with the following error: > error[E0554]: `#![feature]` may not be used on the stable release channel This might not be exactly due to Rust, but only a personal choice made by the project's authors. However, lack of stability does not bode well for the project's longevity and adoption rate.
- prohobo 6y ago
  From what I understand, that might just be a problem with the README. You might have to set your compiler to enable experimental feature flags (thus setup a different compilation channel).
  - wolco 6y ago
    I think the point was if #feature is using the experimental channel and not the stable channel memory stability wasn't as important to the project as it was to him.
    - untog 6y ago
      That’s quite the stretch. Rust’s unstable branch isn’t a total Wild West, it’s just for new features that aren’t ready for stable yet. If you’re not expecting version 1.0 for quite some time it isn’t a problem to use an unstable channel.
    - Ar-Curunir 6y ago
      that feature doesn't even affect memory safety, and is purely for improved ergonomics. It can be removed without affecting the code.

steveklabnik 6y ago

Rust doesn’t prevent leaks, by the way, though it doesn’t tend to produce them.

Filligree 6y ago
Rust forces you to think about ownership. It doesn't prevent leaks, but it does put you in the right frame of mind to not write them.

untog 6y ago

One thing that interests me about using Rust for a project like this is modularity. The Rust toolchain makes it so easy to work with separate crates that it feels very natural to split your work at logical points. C++ doesn’t have that kind of baked in toolchain and just the act of downloading and compiling the Chromium code is a pretty intimidating prospect. If I could easily download and test, say, a CSS parsing module that could be really useful outside of regular browser contexts.

rumanator 6y ago

> I wonder how Rust will influence the outcome of this project? Currently the project fails to build with the following error: > error[E0554]: `#![feature]` may not be used on the stable release channel This might not be exactly due to Rust, but only a personal choice made by the project's authors. However, lack of stability does not bode well for the project's longevity and adoption rate.

prohobo 6y ago
From what I understand, that might just be a problem with the README. You might have to set your compiler to enable experimental feature flags (thus setup a different compilation channel).
- wolco 6y ago
  I think the point was if #feature is using the experimental channel and not the stable channel memory stability wasn't as important to the project as it was to him.
  - untog 6y ago
    That’s quite the stretch. Rust’s unstable branch isn’t a total Wild West, it’s just for new features that aren’t ready for stable yet. If you’re not expecting version 1.0 for quite some time it isn’t a problem to use an unstable channel.
  - Ar-Curunir 6y ago
    that feature doesn't even affect memory safety, and is purely for improved ergonomics. It can be removed without affecting the code.