<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vue.js on No Semicolons</title><link>https://nosemicolons.com/tags/vue.js/</link><description>Recent content in Vue.js on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 02 Aug 2026 09:49:28 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/vue.js/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Framework Wars: How to Pick the Right Model for React vs Angular vs Vue in 2024</title><link>https://nosemicolons.com/posts/ai-code-generation-framework-wars-react-angular-vue-2024/</link><pubDate>Sun, 02 Aug 2026 09:49:28 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-framework-wars-react-angular-vue-2024/</guid><description>&lt;p>Ever found yourself staring at three different AI chat windows, wondering which one will actually generate the React component you need without breaking your entire app? Yeah, me too.&lt;/p>
&lt;p>I&amp;rsquo;ve spent the last month putting GPT-4, Claude, and Gemini through their paces across React, Angular, and Vue projects. What I discovered might surprise you — and it&amp;rsquo;ll definitely save you some debugging headaches.&lt;/p>
&lt;h2 id="the-great-ai-code-generation-experiment">The Great AI Code Generation Experiment&lt;/h2>
&lt;p>Here&amp;rsquo;s what I did: I gave each AI model identical tasks across all three frameworks. Think real-world stuff like building a data table with sorting, creating a form with validation, and setting up routing guards. No toy examples — actual components you&amp;rsquo;d ship to production.&lt;/p></description></item></channel></rss>