4 ms·

Building a native C# implementation of CEL engine

58 points by jackedEngineer 2mo ago

xeonax 2mo ago
This seems like it might be good way to guard state transitions in my PLM/PDM project
nu11ptr 2mo ago
> It’s the language behind Kubernetes admission policies, Envoy’s RBAC rules, Google Cloud IAM conditions, and gRPC’s protovalidate Very small nitpick, but AFAIK protovalidate comes from Buf, not Google. While protovalidate DOES work with gRPC via backward compatibility (but also Buf's ConnectRPC), saying "gRPC's protovalidate" probably makes people think it came from Google. Disclaimer: I have no affiliation with either Buf or Google.
- akshayshah 2mo ago
  Very fair point that protovalidate comes from Buf, not Google. But it's worth noting that protovalidate can also work with plain gRPC - it's an independent library, and anyone can write a gRPC interceptor that uses it. Here's a community-supported example in Go: https://pkg.go.dev/github.com/grpc-ecosystem/go-grpc-middleware/v2/interceptors/protovalidate https://pkg.go.dev/github.com/grpc-ecosystem/go-grpc-middlew...
- javier2 2mo ago
  I think its more important that protovalidate is not affiliated with grpc in any way. One needs a custom middleware to implement the protovalidate rules for your language used.
akshayshah 2mo ago
I'm surprised (without any particular positive/negative valence) that the article doesn't mention using AI to write the port - especially since both CEL and protovalidate have fairly extensive conformance testing harnesses. The project should be right in the sweet spot for today's tools. The omission is especially striking since most of the article sounds AI-authored to me. (Pangram agrees, for what that's worth.)
- progbits 2mo ago
  The code is also clearly all vibecoded. I think this is the usual we get these days: "Show HN: I built..." where in fact author did write neither the code nor the writeup.
  - deleted 2mo ago
    [deleted]
  - rawling 2mo ago
    Is the "chore" commit subject prefix an AI thing? I've started seeing that at work too...
    - vizzier 2mo ago
      Not an AI thing per-se [1] but may be pushed by or increased in usage by the agents. [1] https://www.conventionalcommits.org/en/v1.0.0/#summary https://www.conventionalcommits.org/en/v1.0.0/#summary
    - jmkni 2mo ago
      Semantic git commits have been a thing for years - https://www.conventionalcommits.org/en/v1.0.0/ https://www.conventionalcommits.org/en/v1.0.0/ I've always liked them and tried to convince others to use them AI models seem to like them as well
    - vips7L 2mo ago
      This was a thing before LLMs, but you’d frequently see it in open source repos. So LLMs are just regurgitating what they saw.
    - pcdevils 2mo ago
      Used it for years in part because of https://git-cliff.org/ https://git-cliff.org/
- ameliaquining 2mo ago
  Maybe they just didn't want to deal with people arguing about our field's current omnipresent discourse topic in the context of their project?

This seems like it might be good way to guard state transitions in my PLM/PDM project

> It’s the language behind Kubernetes admission policies, Envoy’s RBAC rules, Google Cloud IAM conditions, and gRPC’s protovalidate Very small nitpick, but AFAIK protovalidate comes from Buf, not Google. While protovalidate DOES work with gRPC via backward compatibility (but also Buf's ConnectRPC), saying "gRPC's protovalidate" probably makes people think it came from Google. Disclaimer: I have no affiliation with either Buf or Google.

akshayshah 2mo ago
Very fair point that protovalidate comes from Buf, not Google. But it's worth noting that protovalidate can also work with plain gRPC - it's an independent library, and anyone can write a gRPC interceptor that uses it. Here's a community-supported example in Go: https://pkg.go.dev/github.com/grpc-ecosystem/go-grpc-middleware/v2/interceptors/protovalidate https://pkg.go.dev/github.com/grpc-ecosystem/go-grpc-middlew...
javier2 2mo ago
I think its more important that protovalidate is not affiliated with grpc in any way. One needs a custom middleware to implement the protovalidate rules for your language used.

akshayshah 2mo ago

I'm surprised (without any particular positive/negative valence) that the article doesn't mention using AI to write the port - especially since both CEL and protovalidate have fairly extensive conformance testing harnesses. The project should be right in the sweet spot for today's tools. The omission is especially striking since most of the article sounds AI-authored to me. (Pangram agrees, for what that's worth.)

progbits 2mo ago
The code is also clearly all vibecoded. I think this is the usual we get these days: "Show HN: I built..." where in fact author did write neither the code nor the writeup.
- deleted 2mo ago
  [deleted]
- rawling 2mo ago
  Is the "chore" commit subject prefix an AI thing? I've started seeing that at work too...
  - vizzier 2mo ago
    Not an AI thing per-se [1] but may be pushed by or increased in usage by the agents. [1] https://www.conventionalcommits.org/en/v1.0.0/#summary https://www.conventionalcommits.org/en/v1.0.0/#summary
  - jmkni 2mo ago
    Semantic git commits have been a thing for years - https://www.conventionalcommits.org/en/v1.0.0/ https://www.conventionalcommits.org/en/v1.0.0/ I've always liked them and tried to convince others to use them AI models seem to like them as well
  - vips7L 2mo ago
    This was a thing before LLMs, but you’d frequently see it in open source repos. So LLMs are just regurgitating what they saw.
  - pcdevils 2mo ago
    Used it for years in part because of https://git-cliff.org/ https://git-cliff.org/
ameliaquining 2mo ago
Maybe they just didn't want to deal with people arguing about our field's current omnipresent discourse topic in the context of their project?