<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Libbpf on Mi&amp;Bee Blog</title><link>/en/tags/libbpf/</link><description>Recent content in Libbpf on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Fri, 26 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/libbpf/rss.xml" rel="self" type="application/rss+xml"/><item><title>eBPF Language Battle: Full-Stack Comparison of C, Rust, and Zig</title><link>/en/posts/telemetry/ebpf-zig-lang-dev/</link><pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate><guid>/en/posts/telemetry/ebpf-zig-lang-dev/</guid><description>&lt;p&gt;The previous articles on OOM tracing all used C for eBPF kernel-space programs. This is natural — C is eBPF&amp;rsquo;s &amp;ldquo;native language,&amp;rdquo; with the verifier, CO-RE, and libbpf toolchain all designed around C. But if you&amp;rsquo;ve followed the eBPF ecosystem, you&amp;rsquo;ll notice a clear trend: &lt;strong&gt;more and more people are writing eBPF in languages other than C&lt;/strong&gt;. Rust&amp;rsquo;s Aya framework is already used in production by the Solana validator and Kubernetes Gateway API; meanwhile, Zig is trying to bring a new development experience with &lt;code&gt;comptime&lt;/code&gt;, explicit allocation, and first-class C interop.&lt;/p&gt;</description></item></channel></rss>