Building a native C# implementation of CEL engine

akshayshah an hour ago | parent | next [-]

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 27 minutes ago \| parent [-]
		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.

▲

nu11ptr an hour ago | parent | prev | next [-]

> 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.

	▲	javier2 8 minutes ago \| parent \| next [-]
		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 an hour ago \| parent \| prev [-]
		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-middlew...

▲

xeonax an hour ago | parent | prev [-]

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