Re:Rust-GPU: Making Rust a first-class language and ecosyste...
by pjmlp on Saturday October 24, 2020 @10:01AM
(#24879275)
The browser vendors for example.
Re:Rust-GPU: Making Rust a first-class language and ecosyste...
by creata on Saturday October 24, 2020 @10:34AM
(#24879421)
Is it really the case they "have already learned to scale down from threads"? I'm obviously not well-versed in browser internals, but here's the very first sentence of "Threading and Tasks in Chrome":
> Chrome has a multi-process architecture and each process is heavily multi-threaded.
https://chromium.googlesource.com/chromium/src/+/master/docs...
Either way, I think browsers have a very specific scenario, where there isn't much interaction between the tabs, and they need to be well-isolated from each other. I don't think that's a good reason for everyone else to move away from threads.
Re:Rust-GPU: Making Rust a first-class language and ecosyste...
by pjmlp on Saturday October 24, 2020 @11:15AM
(#24879677)
That's a very good point, and maybe I'm being needlessly pedantic by considering it a part of the current (and only) implementation rather than a fundamental part of the language.
> We have already learned to scale down from threads and go back to processes for security and stability reasons.
Who is "we"? I still see a lot of parallel code being written with threads or async/await, and Rust's ownership system gives additional safety in both cases.