<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MainActor on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/mainactor/</link><description>Recent content in MainActor on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 26 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/mainactor/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 14: Concurrency - Async/Await &amp;amp; Tasks</title><link>https://ai-blog.noorshomelab.dev/mastering-swift-2026/14-concurrency-async-await-tasks/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-swift-2026/14-concurrency-async-await-tasks/</guid><description>&lt;h2 id="chapter-14-concurrency---asyncawait--tasks"&gt;Chapter 14: Concurrency - Async/Await &amp;amp; Tasks&lt;/h2&gt;
&lt;p&gt;Welcome back, future Swift master! So far, you&amp;rsquo;ve built a solid foundation in Swift&amp;rsquo;s syntax, types, control flow, and even how to handle errors and manage memory. You&amp;rsquo;re becoming quite the wizard! But what happens when your app needs to do something time-consuming, like fetching data from the internet or processing a large image? If you do it directly on the main thread (the one responsible for your app&amp;rsquo;s user interface), your app will freeze, becoming unresponsive and frustrating for the user. Nobody likes a frozen app!&lt;/p&gt;</description></item></channel></rss>