<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SVG on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/svg/</link><description>Recent content in SVG 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/svg/rss.xml" rel="self" type="application/rss+xml"/><item><title>From Mermaid to WebGPU: Four Diagram Mistakes in a Year of Blogging</title><link>https://blog.mickeyzzc.tech/en/posts/aihelper/frontend-chart-tech-history/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/aihelper/frontend-chart-tech-history/</guid><description>&lt;p&gt;I&amp;rsquo;ve been blogging for over a year now, and I&amp;rsquo;ve drawn dozens of diagrams. Architecture diagrams, sequence diagrams, data comparison bar charts, TCP congestion window evolution curves.&lt;/p&gt;
&lt;p&gt;Then one day on my commute home, it hit me: &lt;strong&gt;I&amp;rsquo;ve been using Mermaid almost daily, but I have no idea what technology powers it.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;You write a &lt;code&gt;```mermaid&lt;/code&gt; code block, save the file, and there it is—a fully rendered diagram. But how does text become SVG? What even &lt;em&gt;is&lt;/em&gt; SVG? Why do I use Chart.js for bar charts and ECharts for stacked line charts? What if I need a real-time dashboard, not just a static diagram?&lt;/p&gt;</description></item><item><title>Frontend Graphics Evolution: From HTML Tables to WebGPU</title><link>https://blog.mickeyzzc.tech/en/posts/aihelper/frontend-chart-tech-evolution/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/aihelper/frontend-chart-tech-evolution/</guid><description>&lt;p&gt;Before choosing technology, understand the landscape.&lt;/p&gt;
&lt;p&gt;Many developers encountering frontend visualization for the first time dive straight into a framework&amp;rsquo;s documentation, slowly grind through configuration options, and eventually produce a working chart. But months later, when they hit performance bottlenecks or need to support more complex interactions, they realize the tool they chose doesn&amp;rsquo;t fit their needs.&lt;/p&gt;
&lt;p&gt;The evolution of frontend graphics technology follows a very clear trajectory. Understanding this trajectory keeps you from getting lost when selecting tools.&lt;/p&gt;</description></item><item><title>SVG, Canvas, WebGL: Choosing Your Rendering Layer</title><link>https://blog.mickeyzzc.tech/en/posts/aihelper/frontend-chart-rendering-tech/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/aihelper/frontend-chart-rendering-tech/</guid><description>&lt;p&gt;We covered chart history and tool selection in previous posts. Now let&amp;rsquo;s go technical: how do you choose between SVG, Canvas, and WebGL rendering layers?&lt;/p&gt;
&lt;p&gt;Many developers have a misconception: SVG is slowest, Canvas is medium, WebGL is fastest. Like a transportation hierarchy—bicycle, car, airplane. But this intuition is wrong.&lt;/p&gt;
&lt;h2 id="essential-differences-three-rendering-modes"&gt;Essential Differences: Three Rendering Modes&lt;/h2&gt;
&lt;p&gt;Here&amp;rsquo;s the bottom line: the core difference between these technologies isn&amp;rsquo;t performance, it&amp;rsquo;s rendering mode.&lt;/p&gt;</description></item></channel></rss>