Comment by pshc

Excerpt from Graydon's (BDFL) reply:

  > Despite all these caveats I have a very strong sense that writing the
  > runtime in Rust will go a long way to validate Rust in the domains it's
  > aiming for: concurrent and systems programming. Even in the task
  > scheduler, where there's quite a bit of unsafe code, the shared-nothing
  > nature of unique types forces you to consciously break the type system
  > to share memory, and that seems to go a long way to making parallel
  > programming easier to reason about.

  Yes, even just reading it seems much clearer since the mutability, 
  lifetime and ownership of each value and reference is spelled out, not 
  just "some Foo* that you have to remember special validity rules about". 
  It's noticeably easier to reason about. Really interesting!

When Rust matures (and this dogfooding-via-self-bootstrap is going to accelerate its maturation) it's going to be seriously revolutionary for, for example, modern multi-core video game development. Really excited.