Sysprof redesign
Sysprof needs a redesign pretty badly. It's sort of just hopped along on one leg since the initial revamp based on ideas I had a decade ago for another profiler app.
That said ... We should probably put together some use cases that will help guide things along the way.
Maybe @YaLTeR @otte @matthiasc and others could chime in with some ways they are using the apps so we can collect those.
The current "front page" is the way it is because I was trying to preserve a feature that @otte liked, which was open, hit enter, hit escape, see callgraph. But if we diverged from this a bit, we can probably make something that allows for a flow which is "task" or "problem" oriented. Such as "Find a memory leak".
We probably want to use something like Instruments on macOS as a guidepost, as it's probably the simplest-yet-good-outcomes I've seen.
It might also be nice to take a look at Kernel Shark and see how we can draw data similarly (it's really handle at debugging scheduler issues).
We can certainly add new data recorders to make solving some of these problems possible in Sysprof. Additionally, we probably will want some sort of basic "syntax language" for filtering events.
Firefox's profiler is also probably one of the better things out there to take inspiration from in terms of the waterfall/marks graphs.