<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rust on BareProxy.com</title>
    <link>https://bareproxy.com/tags/rust/</link>
    <description>Recent content in Rust on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy 0.3.0 Writes Its Plugins in Rust, Where a Plugin Adds 15 Microseconds Instead of 42</title>
      <link>https://bareproxy.com/bareproxy-0.3.0-writes-its-plugins-in-rust-where-a-plugin-adds-15-microseconds-instead-of-42/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-0.3.0-writes-its-plugins-in-rust-where-a-plugin-adds-15-microseconds-instead-of-42/</guid>
      <description>&lt;p&gt;BareProxy 0.3.0 is out. It doesn&amp;rsquo;t ship a plugin yet. It settles how the plugins get written: in Rust, with the Proxy-Wasm Rust SDK, the same one Envoy plugins use.&lt;/p&gt;&#xA;&lt;p&gt;The question was speed. The first test plugin was written in Go, and a Go plugin carries Go&amp;rsquo;s runtime into every call. So a Rust test plugin now does everything the Go one does, and the plugin host&amp;rsquo;s tests run with both on every push. The real SDK worked with the host as it was.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
