<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Threads on Nalar</title>
    <link>https://nalar.dev/tags/threads/</link>
    <description>Recent content in Threads on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/threads/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Language Runtimes Use CPU Cores: Threads, Goroutines, Workers, and Processes</title>
      <link>https://nalar.dev/how-language-runtimes-use-cpu-cores-threads-goroutines-workers-and-processes/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/how-language-runtimes-use-cpu-cores-threads-goroutines-workers-and-processes/</guid>
      <description>&lt;p&gt;A CPU with many cores does not make application code parallel by itself. The operating system can schedule multiple threads at the same time, but the language and runtime decide how application work reaches those threads. That distinction explains why Go, Rust, C++, Java, JavaScript, and PHP can all use a multicore machine even though their programming models look very different.&lt;/p&gt;&#xA;&lt;p&gt;The useful question is not simply whether a language is &amp;ldquo;multithreaded.&amp;rdquo; It is how a unit of application work becomes something the operating system can schedule.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
