2 ms·
It's a fun Rust thing. People stand up websites to expose a high level view of Rust's ability to fit the needs of a given field and to inspire and encourage fas
by echelon 4y ago
It's a fun Rust thing. People stand up websites to expose a high level view of Rust's ability to fit the needs of a given field and to inspire and encourage faster work.
- https://areweasyncyet.rs/ https://areweasyncyet.rs/
- https://www.areweguiyet.com/ https://www.areweguiyet.com/
- https://areweideyet.com/ https://areweideyet.com/
- https://www.arewewebyet.org/ https://www.arewewebyet.org/
A whole list: https://wiki.mozilla.org/Areweyet https://wiki.mozilla.org/Areweyet
- nindalf 4y agoThere used to be arewefastyet.rs, to measure the speed of the compiler. But I didn't renew the domain. It's at https://arewefastyet.pages.dev https://arewefastyet.pages.dev now.
- dralley 4y agohttps://perf.rust-lang.org/ https://perf.rust-lang.org/
- nindalf 4y agoThe FAQ I wrote answers the question - "What does this website show that perf.rust-lang.org doesn't?" - perf.rust-lang.org is great for monitoring for regressions on a day to day basis, perfect for compiler devs. But arewefastyet.rs aims to answer other questions, like - How much rustc has improved on certain workloads over a long time period. - How rustc performance is affected by different hardware. 8 cores is better than 4, all other things being equal, but how much more? On which workloads? - How much time in seconds it actually takes to compile common crates. Concerns about developer productivity could be allayed by seeing the number of seconds it takes to compile a complex binary like ripgrep.
- dralley 4y agoMore like a Mozilla thing that got adopted by Rust.