<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Concurrency on Home</title><link>https://oedokumaci.com/tags/concurrency/</link><description>Recent content in Concurrency on Home</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Oral Ersoy Dokumaci</copyright><lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://oedokumaci.com/tags/concurrency/index.xml" rel="self" type="application/rss+xml"/><item><title>Why the Hardest Concept for Python Devs Is Concurrency: asyncio vs threading vs multiprocessing</title><link>https://oedokumaci.com/blog/posts/python-concurrency/</link><pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate><guid>https://oedokumaci.com/blog/posts/python-concurrency/</guid><description>Concurrency is arguably the hardest concept for Python developers, because the important ideas already assume you understand the operating system underneath. In this chapter, we start from the kernel and system calls, build up processes, threads, race conditions, and the GIL, then work out when to reach for asyncio, threading, or multiprocessing, why a GPU beats a CPU on the same arithmetic, and how to get better at concurrent programming.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://oedokumaci.com/blog/posts/python-concurrency/featured.jpg"/></item></channel></rss>