I remember years ago there was a very obvious console message (related to an invalid date) that was spamming the system log frequently for at least a month, acr

I remember years ago there was a very obvious console message (related to an invalid date) that was spamming the system log frequently for at least a month, across multiple minor OS updates, in nearly every application. It was actually noticeably impacting the CPU because it appeared so often. Now I’m wondering if this console “rewrite” happened around the same time, perhaps in response to it. Maybe after seeing one difficult-to-wrangle log message, they concluded that gaining complete control over all logging was the only solution? In any case, they went way too far. Console is effectively useless now; I got so tired of opening it up and finding nothing of value that I stopped even looking, and just apply every other possible debugging method first. Their push for multi-process solutions like XPC have made logging even more useless because by default the new log system refuses to show output from sub-processes AT ALL. So imagine an app that previously had a nice sequential log for in-process actions A, B, and C; after migrating to sub-processes, now you see only the output of action B because the A and C actions are in different sub-processes! While there is a way to enable the output from all of them, it’s not the default and it’s not obvious and it’s just another stupid debugging hurdle.