3 ms·
> One way that Rust compiles way slower than C++ is its Gentoo approach to libraries. With C++ I only compile my own code. That's a very good point, and maybe
by creata 6y ago
> One way that Rust compiles way slower than C++ is its Gentoo approach to libraries. With C++ I only compile my own code.
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.
- pjmlp 6y agoThe browser vendors for example.
- creata 6y agoIs 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/threading_and_tasks.md 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.
- pjmlp 6y agoHere are another examples then, https://docs.microsoft.com/en-gb/azure-sphere/product-overview/what-is-azure-sphere#azure-sphere-architecture https://docs.microsoft.com/en-gb/azure-sphere/product-overvi... https://source.android.com/devices/architecture/hal-types?hl=en https://source.android.com/devices/architecture/hal-types?hl... https://developer.apple.com/documentation/driverkit https://developer.apple.com/documentation/driverkit