Speaking of excuses. Things such as the JVM, .NET and Go both have more of a need for profiling, as well as often an easier time. They are always constructed out of multiple agents that most people did not program themselves and certainly don't understand entirely (prominent example being the garbage collectors) and they have a default async runtime. Rust doesn't have the first issue, at least not to the same degree, while the 2nd issue is, in most situations, sadly a negative for Rust. Rusts choice against a Runtime has sadly yet to pay off entirely. Using Rust async on stuff such as embedded is only just getting out of alpha with stuff such as embassy-rs getting released, and many runtimes are incompatible, hurting the ability to adopt a purpose built runtime. But excuses aside. It's true, in practice there is an acute lack of either the tools for profiling, or their active usage.
![Kodak Black - Versatile 4 [Official Video]](http://i.ytimg.com/vi/VcP_1Ua__vY/mqdefault.jpg)
Fantastic, thank you. Perf analysis is very important!
Important topic! Thanks.
Really liked the presentation!
Speaking of excuses. Things such as the JVM, .NET and Go both have more of a need for profiling, as well as often an easier time.
They are always constructed out of multiple agents that most people did not program themselves and certainly don't understand entirely (prominent example being the garbage collectors) and they have a default async runtime.
Rust doesn't have the first issue, at least not to the same degree, while the 2nd issue is, in most situations, sadly a negative for Rust. Rusts choice against a Runtime has sadly yet to pay off entirely. Using Rust async on stuff such as embedded is only just getting out of alpha with stuff such as embassy-rs getting released, and many runtimes are incompatible, hurting the ability to adopt a purpose built runtime.
But excuses aside. It's true, in practice there is an acute lack of either the tools for profiling, or their active usage.