Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New Rust runtime turned on. What next?

mail.mozilla.org

Post reply on HN
Print view View original

1–10 of 118 posts

Re: New Rust runtime turned on. What next?

#2

Post 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.

Re: New Rust runtime turned on. What next?

#3

Post by zhemao »

pshc wrote: post #2

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…

Yes, please. Anything but C++. The progress of Rust and Go make me hopeful for the future.

Re: New Rust runtime turned on. What next?

#4

Post by agumonkey »

pshc wrote: post #2

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…

> dogfooding-via-self-bootstrap

Very rare thing. Ok maybe not in language design. But rare otherwise.

Re: New Rust runtime turned on. What next?

#7

Post by pkulak »

> it does implement TCP and UDP on both IPv4 and IPv6

I thought this sort of thing was usually handled by the OS. Can you even get raw sockets on most systems? Or by "implemented TCP", do they mean they can give you back a Unix TCP/UDP socket?

Re: New Rust runtime turned on. What next?

#9

Post by charliesome »

zhemao wrote: post #3
pshc wrote: post #2

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…

Yes, please. Anything but C++. The progress of Rust and Go make me hopeful for the future.

Go (at least as it stands today with its non-generational, stop the world, mark and sweep GC) is wholly unsuitable for video game development where unpredictable latency must be avoided.
Post reply on HN