<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bokeh on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/bokeh/</link>
    <description>Recent content in Bokeh on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 18 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/bokeh/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>matplotlib vs Plotly vs Bokeh in 2026: Which Python Visualization Library Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-18-matplotlib-vs-plotly-vs-bokeh-python-visualization-comparison/</link>
      <pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-18-matplotlib-vs-plotly-vs-bokeh-python-visualization-comparison/</guid>
      <description>&lt;p&gt;Data visualization is where data science projects go to die or get funded, and the Python ecosystem&amp;rsquo;s three heavyweights — matplotlib, Plotly, and Bokeh — look interchangeable until the moment your stakeholder asks for something specific: a publication-ready PDF figure, a zoomable dashboard with live streaming data, or a chart embedded in a web app. Pick the wrong one and you spend a week fighting the API to do what the other library does in three lines.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
