Over the last few months I've accumulated many triggers which I made myself - for myself, tailored to my needs. I learned to solve every little inconvenience with a trigger to patch those QoL needs allover the OS and in various third-party apps.
though theres no doubt that some of my solutions are probably very clunky and in some cases overkill - and I have a rising suspicion that ive accumulated performance tax on my everyday usage with all those triggers.
I cant tell which triggers are completely fine and harmless to have around, and which ones activate 1000 times a second for whatever reason or require a very high load of performance either by nature or by my own bad implementation/incorrect usage…
I wish there was a more refined view - just like the - “recently used” which is definitely helpful; but also one that can mention if a trigger is “unhealthy” for performance - triggers suspiciously too often / or simply drop performance in general.. trying to hunt these conclusion with the Activity Monitor would be inefficient…
I just wanna be able to pinpoint what causes those odd stutters / random frame drops / non-smooth experience here and there, to fix/disable it…
if its something that is realistic to implement that could be very useful I believe!
