Have conditions as separate entity will help to reuse condition across Rules. Currently its more of rewriting same across onn Rules( which can help to trigger diffrent tags on same set to cinditions).
Hope it make sense.
I work around this by writing a "Custom Code" Data element, and use that data element as a condition. This creates a condition that can be reused. But yes, I think a "Conditions" feature could be nice so Conditions could be written in a simpler way.
There already is an idea with the same basic premisse: Reuse events, conditions, exceptions in rules
Thanks for pointing out the existing idea. I've archived this idea so support doesn't end up getting split between them.