<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vision on BareProxy.com</title>
    <link>https://bareproxy.com/tags/vision/</link>
    <description>Recent content in Vision 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/vision/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy Is an Operating System for Web Traffic: A Small Core and a Long Stream of Plugins</title>
      <link>https://bareproxy.com/bareproxy-is-an-operating-system-for-web-traffic-a-small-core-and-a-long-stream-of-plugins/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-is-an-operating-system-for-web-traffic-a-small-core-and-a-long-stream-of-plugins/</guid>
      <description>&lt;p&gt;BareProxy started as a question: how little machinery does it take to do the part of nginx most sites use? The answer turned out to be a small core. With plugins in place since 0.2.0, it has become something more useful to describe as an operating system for web traffic.&lt;/p&gt;&#xA;&lt;p&gt;The comparison is meant as a way to see how the parts fit. BareProxy doesn&amp;rsquo;t run hardware. But it has the same shape as a good operating system, and the shape explains the design.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
