<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Composition API vs. Options API - One API to Rule Them All?!</title>
        <link>https://tube.grossholtz.net/videos/watch/f26fdad1-c2a2-44df-a968-9fe247e38c07</link>
        <description>💪 This week was a lot of discussion about the two Vue APIs - the Composition and the Options API - on Social Media. Thus, I took some time to assess the shared thoughts + discussions and also went a step further: I asked you why you prefer the Options API and wanted to figure out pain points you have with the Composition API. The results are all distilled in this video, including what the Vue team and Evan say about the API topic, how the future might look like and my personal opinion (at the very end). Important Disclaimer: I am not part of the Vue core team (but the Nuxt team). I researched all quotes and facts with care, links are commonly below to the topics, tweets and posts! #vuejs Links 🔗 FREE VueSchool Composition API Course - https://vueschool.io/courses/vue-js-fundamentals-with-the-composition-api?friend=ALEX * 🔗 Justin’s Proposal https://x.com/jpschroeder/status/1797733354533711994 🔗 Justin Doubling Down https://x.com/jpschroeder/status/1798009086853697839 🔗 Vue Docs on deprecating Options API https://vuejs.org/guide/extras/composition-api-faq.html#will-options-api-be-deprecated 🔗 Evan Clarifying CAPI vs OAPI https://x.com/youyuxi/status/1798542270695960803 🔗 Vue Docs - Why Composition API? https://vuejs.org/guide/extras/composition-api-faq.html#why-composition-api 🔗 Unplugin for script setup https://github.com/unplugin/unplugin-vue2-script-setup 🔗 Cory House SOC https://x.com/housecor/status/1256348777331470340 🔗 Infographic Vue SOC OAPI https://img.lichter.io/infographics/vue-soc-oapi.png 🔗 Infographic Vue SOC CAPI https://img.lichter.io/infographics/vue-soc-capi.png 🔗 Infographic Vue SOC Both https://img.lichter.io/infographics/vue-soc-both.png 📺 Organizing Code with the Composition API https://www.youtube.com/watch?v=iKaDFAxzJyw 📺 You probably use useFetch wrong https://www.youtube.com/watch?v=njsGVmcWviY 📺  @DejaVueFm Episode 011 about Learning new Vue Features https://www.youtube.com/watch?v=bg3hdQwZzAw Don't forget to hit that "Subscribe" button, ring the notification bell and give a thumbs up! 🌐 Connect further: Website: https://www.lichter.io Twitter/X: https://twitter.com/TheAlexLichter Twitch: https://www.twitch.tv/TheAlexLichter Chapters 00:00 Intro 00:39 Should People Learn the Options or Composition API? 01:39 Will the Options API Go AWAY? 05:17 Why NOT Using the Composition API? 05:44 Argument One: Legacy 07:55 Argument Two: Compatibility 08:39 Argument Three: Reactivity 11:20 Argument Four: Structure / Messy Code 13:45 Separation of Concerns 17:56 Further Benefits of the Composition API 19:50 The Ecosystem 21:24 My Personal Opinion 24:39 Summary Notice Links marked with * are affiliate links. I get a small commission when you register for the service through our link. This helps to keep the YouTube channel running. I only include affiliate links for services mentioned in the video which I use myself and/or vouched!</description>
        <lastBuildDate>Mon, 06 Apr 2026 03:13:27 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://tube.grossholtz.net</generator>
        <image>
            <title>Composition API vs. Options API - One API to Rule Them All?!</title>
            <url>https://tube.grossholtz.net/client/assets/images/icons/icon-512x512.png</url>
            <link>https://tube.grossholtz.net/videos/watch/f26fdad1-c2a2-44df-a968-9fe247e38c07</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://tube.grossholtz.net/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://tube.grossholtz.net/feeds/video-comments.xml?videoId=f26fdad1-c2a2-44df-a968-9fe247e38c07" rel="self" type="application/rss+xml"/>
    </channel>
</rss>