<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chart.js on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/chart.js/</link><description>Recent content in Chart.js on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/chart.js/rss.xml" rel="self" type="application/rss+xml"/><item><title>Choosing a Chart Library: From Chart.js to D3.js</title><link>https://blog.mickeyzzc.tech/en/posts/aihelper/frontend-chart-library-guide/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/aihelper/frontend-chart-library-guide/</guid><description>&lt;p&gt;With so many chart libraries out there, Chart.js, ECharts, D3, Highcharts, AntV, Plotly, Recharts, Victory&amp;hellip; the first thing to get straight is: they&amp;rsquo;re fundamentally not substitutes for each other.&lt;/p&gt;
&lt;p&gt;Config-driven factories vs parts toolboxes — that&amp;rsquo;s the essential difference. D3.js is the bottom-up toolbox where you assemble parts yourself. ECharts and Highcharts are config-driven factories where declarative configuration produces charts. Recharts and Victory are React native component libraries with declarative being most natural. Get this positioning difference right, and you&amp;rsquo;re halfway there.&lt;/p&gt;</description></item></channel></rss>