Simple: when running on older macOS, remove some items from the app menu. The solution is also straightforward, just very hard to locate.
Swift Playgrounds are attracting a lot of young people to learn to code. But what do they do when they’re ready to write ‘proper’ apps? Where are Apple’s guides and example code?
At last: RouteMap performs some analysis on your Signposts, and with the other tools can be used to estimate latency, and look at macOS system performance too.
Picking the right time system for the purpose is critical when you want to analyse very short periods. Sometimes it takes time to discover how to juggle with time.
Doesn’t writing so much to the unified log result in performance penalties? So how can Apple expect us to use the log and Signposts to measure performance?
Blowhole 7 now writes proper Signposts in Mojave, as well as Pseudo-Signposts in Sierra and High Sierra.
At first I thought it was my mistake. Then it looked like a simple error in the interface. But this bug in Mojave’s signposts is more complex. Here’s a workaround.
A new version of Blowhole, the second alpha of RouteMap, and a complete tutorial toolkit to help you get started using log Signposts from Sierra to Mojave.
Do you want to measure performance or get other info from your app or script? Using Signposts is ideal, and here’s the first glimpse of a new tool to harvest them.
While we’re worrying about 32-bit apps, something else is changing which is likely to stop many more apps from working properly. In the near future.