<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rule-Engines on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/rule-engines/</link>
    <description>Recent content in Rule-Engines on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/rule-engines/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Embedded Expression Languages in 2026: CEL vs expr-lang vs JSONata vs Starlark</title>
      <link>https://www.pistack.xyz/posts/2026-09-27-expression-languages-cel-go-expr-lang-jsonata-starlark-comparison/</link>
      <pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-27-expression-languages-cel-go-expr-lang-jsonata-starlark-comparison/</guid>
      <description>&lt;p&gt;The feature request always arrives the same way: &lt;em&gt;&amp;ldquo;can we write our own filter rules without waiting for your release cycle?&amp;rdquo;&lt;/em&gt; You have two options. Either you build a plugin SDK that nobody adopts because it requires a compiler and a code review, or you embed an expression language and let users write &lt;code&gt;severity == &#39;critical&#39; &amp;amp;&amp;amp; service in allowed_services&lt;/code&gt;. The second option is a product decision with a security dimension, and the language you pick decides how much of that dimension you have to own.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
