<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Javascript on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/javascript/</link>
		<description>Recent content in Javascript on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 20 Jul 2026 18:45:00 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/javascript/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 execution order is predictable when three layers are kept separate: synchronous execution on the current stack, work queued by the host environment, and the checkpoints where queued callbacks become eligible to run. Browser event loops distinguish tasks from microtasks and coordinate rendering opportunities, while Node.js organizes host callbacks into event-loop phases with additional queue behavior. The language and each host runtime therefore contribute different parts of the result.&lt;/p&gt;&#xA;&lt;p&gt;&lt;figure&gt;&#xA;    &lt;img src=&#34;https://www.compilemymind.com/posts/javascript-event-loop-tasks-microtasks-rendering/concept-flow.svg&#34; alt=&#34;JavaScript event loop task and microtask reasoning flow&#34; width=&#34;1200&#34; height=&#34;830&#34; loading=&#34;lazy&#34; decoding=&#34;async&#34;&gt;&#xA;    &#xA;  &lt;/figure&gt;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
