microui VS tracy

There is also microui, which I like[0].

Which I forked to work with SDL2[1], no guarantees. It's fun to hack on.

[0]https://github.com/rxi/microui

[1]https://github.com/kennethrapp/microui

I'm not sure if this is what you are looking for but I found https://github.com/wolfpld/tracy to work rather well. There is an integration for the tracing crate that can get you very far: https://lib.rs/crates/tracing-tracy. If you're just looking for a very high level report then this might be a bit too much detail.

> First, this isn't really true. You might typically have a window, a container, a layout object and then your gui components.

Any non-trivial UI will include many complicated workflows and layouts. "GUI components" themselves will often be combinations of other, more primitive, GUI components.

> Second you don't need nested calls, you just add one component to another.

You're just describing currying here (function application or nesting hierarchies are the same thing), and both are equally annoying when building interfaces.

> Why would that be true?

Because you will want certain things to be reusable, it's a pretty common pattern.

> This is a bizarre way to make a GUI let alone thinking it's necessary. Where is this idea coming from?

It's a pretty common pattern for building GUIs. Take a look at tracy[1], built using ImGUI. All the different components are split up in their own file, I'm not sure what the alternative would be, like a 100,000-line "master UI" file? Seems like a much worse idea. Looking at the tracy code, it's very well-written, but also super weird to follow. For example, color defaults seem to be located in header files[2]. I mean, yuck.

[1] https://github.com/wolfpld/tracy/tree/master/profiler/src/pr...

[2] https://github.com/wolfpld/tracy/blob/master/profiler/src/pr...

While it doesn't capture every syscall, you can get pretty far with the (seemingly little known) Endpoint Security Framework: https://developer.apple.com/documentation/endpointsecurity

I cobbled together a little tool at my previous job that would capture a full trace of all process fork+exec and file opens, which would then present all of these events in the usual tracing UI (like you'd get when view a trace of a single program with Tracy[1] or Perfetto[2]).

We had a massive monorepo built with bazel and a heap of shell, and it wasn't clear which part of our code base was responsible for generating some mis-generated file. This tool gave me the whole inter-process call stack, complete with arguments and environment variables, letting me quickly find where and how to fix the problem.

It's such a nice tool to have that it kinda blows my mind that no one has openly published anything like it. By leveraging eBPF on Linux, the same UI could be used on both macOS and Linux. If I had more time and energy, I'd do it myself.

[1]: https://github.com/wolfpld/tracy

[2]: https://perfetto.dev/

https://github.com/wolfpld/tracy/issues/887

MSVC changed the mutex constructor to constexpr, breaking binary backward compatibility. They say WONTFIX, you must use the latest MSVCRT with the latest MSVC. But I have the latest MSVCRT installed? Whatever - a workaround was pushed to master yesterday.

I consider Tracy the state of the art for profiling C++ applications. It’s straightforward to integrate, toggle, gather data, analyze, and respond. It’s also open source, but rivals any product you’d have to pay for:

https://github.com/wolfpld/tracy

For C++ applications, nothing beats Tracy’s flame graphs in value per dollar. We are using it at Adobe with great effect. It can handle mutex lock contention, runtime values and notes, arbitrary value graphs, and more. Highly recommended: https://github.com/wolfpld/tracy

i don't really think there is _anything_ that comes even close to tracy https://github.com/wolfpld/tracy.

on top of this, given google's penchant for dumping projects aka abandonware, this would be an easy pass.