brobot182

It plain looks bad. But also, it requires more scrolling to get to the meat of the project

The layout, at least on mobile, could use some work

Is there a chrome plugin that prevents this?

I have almost the exact same setup as you: same CPU cooler, same CPU, and the pro WiFi version of the Z390. However, when I’m doing a long-running clean build that uses the 16 logical cores, the temperature for each core gets up to 80 C. Any thoughts why that would be?

This performance analysis is not very useful. How taxing an app is on the CPU is not a user-visible metric, unlike, for example, the time it takes from tapping on an app to it being responsive. The taxing of the CPU is only valuable to think about when thinking when analyzing battery impact (and it takes a lot more analysis than what was given). I’d be much more interested to see:

- startup time

- time to transition between screens (and ideally with more views on each screen, eg make two copies of each view)

- differences in network performance, if any

Maybe if you had some super-short typealiases it would work, e.g. ‘typealias UnsafeRawPointer = URP’. Otherwise, you get bogged down with all the casting and other FFI stuff. One alternative besides gdb is cling: https://root.cern.ch/cling