“Simple things should be simple. Complex things should be possible.” - Alan Kay<p>Rust really embodies this imo. I think it will be a few more years, but we're going to be seeing a lot more Rust -- and for good reason.
From a debugger's point of view, Rust is just another native code language. DWARF tells you how to get stacks, find variables, and interpret chunks of memory as data structures. Anyone trying to pitch you a debugger specifically for Rust is trying to ride a hype wave or just plain bamboozle you.
Cool, reminds me somewhat of Glamorous Toolkit [1], another project I just found out about. Excited to give it a try, I love these sort of "explain a program as it's running" type tools.<p>1. <a href="https://gtoolkit.com/" rel="nofollow">https://gtoolkit.com/</a>
Please show me this being used to debug a real program. Toy examples that don’t do any real work isn’t interesting. My confidence that this work for an actual program is approximately zero percent.
Nice project! I’ll be highlighting it in the next edition of the <a href="https://Rust-Trends.com" rel="nofollow">https://Rust-Trends.com</a> newsletter.
This is just a trace viewer. Except the trace visualization is vastly less dense than any standard trace viewer and seems to provide no meaningful execution time information.<p>Compare to chrome://tracing<p><a href="https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/" rel="nofollow">https://www.chromium.org/developers/how-tos/trace-event-prof...</a><p>I am not sure if trace visualizers were invented 20 years ago for the original time travel debuggers, but they have certainly been used for time travel debugging visualization since at least 20 years ago.
I want to use this right now, but two issues:<p>- Bash script from Internet requiring sudo, no way<p>- VSCode plugin? I don't use VSCode. I'm not switching from Zed (literally built in Rust for Rust development)<p>Help me out, what can I do to try this?