Building a native C# implementation of CEL engine

A developer dropped Celly, a brand-new C# version of Google’s Common Expression Language — basically a safe way to let apps read simple rules from text instead of hard-coding them forever. In plain English: this lets teams change things like access rules and data checks without shipping a whole new app update. Big win, right? The community reaction was a mix of "finally!", nitpicking, and the now-obligatory AI side-eye.

One of the most upbeat reactions came from someone already imagining real-world use: this could be a slick way to control how things move through a product management system. That’s the wholesome part of the thread. Then the pedant alarm went off. One commenter jumped in to correct the article’s wording around protovalidate, saying calling it "gRPC’s protovalidate" could mislead people because it came from Buf, not Google. Tiny detail? Maybe. But this is the internet, where small wording choices become courtroom exhibits.

And then came the spiciest twist: a commenter said they were surprised the post didn’t mention using AI to help write the port — especially since the project has lots of official tests. They even added that parts of the article "sound AI-authored", which is the kind of accusation that can turn any comment section into a digital food fight. So while the actual news is that .NET finally gets a fully native, fully tested CEL engine, the comments turned it into a three-ring circus of useful ideas, brand-correction drama, and robot-writing suspicion.