Am I the only one who finds the YARA-L syntax more confusing than Sigma?

Just finished a vendor bake-off between Chronicle and another SIEM. The YARA-L syntax is a blocker for my team.

Everyone liked Sigma rules for their readability. You can almost guess what they do. YARA-L feels like a step backwards. The event section, match section, outcome section... it's more verbose and the logic seems inverted. Writing a simple detection for a suspicious process execution takes more lines and more mental parsing.

I'm responsible for our procurement and long-term tool viability. If my analysts struggle with the primary detection language, that's a direct productivity and risk issue. Am I missing something? Is there a trick to it, or is the learning curve just that steep?