Protip:
When designing a user interface, imagine some old woman using it, say Margaret Hamilton, and she's clicking your app's buttons and saying to you, as old people do,
"Young whippersnapper, when I was your age, I sent 24 people to the ACTUAL MOON with my software in 4K of RAM and here I am clicking your button and it takes ten seconds to load a 50 megabyte video ad and then it crashes
I'm not even ANGRY with you, I'm just disappointed."
@ninjawedding @er1n flame graphs?
@LottieVixen @ninjawedding @er1n profiler output visualization tool, helps you see what functions and system calls your program is spending the most time on
this, or similar (like what erin linked) :
http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html
first image is an example of a flame graph from the QML profiler; you can see that the majority of total time was spent updating a binding (and, amusingly, there's no sub-operation inside it). you can then look at the timeline to see what that looks like over time, which is useful for analyzing things like "what's causing jank" etc and getting an idea of what that 51.7% of time spent means in terms of frame budget
FlameScope does look cool, I just don't know how to integrate it yet :P
@ninjawedding it has perf(1) support 👀
that could make it really easy then 🤔
actually I think you told me about this before lol
@ninjawedding probably lmao