<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Event-Loop on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/event-loop/</link>
		<description>Recent content in Event-Loop on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 26 Jul 2026 18:35:00 +0200</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/event-loop/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>JavaScript Event Loop: Tasks, Microtasks, and Rendering</title>
				<link>https://www.compilemymind.com/posts/javascript-event-loop-tasks-microtasks-rendering/</link>
				<pubDate>Mon, 20 Jul 2026 16:17:58 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/javascript-event-loop-tasks-microtasks-rendering/</guid>
				<description>&lt;p&gt;JavaScript timing becomes much easier when you stop imagining one callback queue. In a browser, the useful model is:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Run the current JavaScript job to completion.&lt;/li&gt;&#xA;&lt;li&gt;At the event loop&amp;rsquo;s checkpoint, drain microtasks.&lt;/li&gt;&#xA;&lt;li&gt;The browser may update rendering.&lt;/li&gt;&#xA;&lt;li&gt;Select another eligible task and repeat.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Node.js also runs JavaScript to completion, but its host loop has phases and Node-specific queues. A browser prediction should not be copied blindly into a Node.js program.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
