diff --git a/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Duoae-i-dont-agree-with-point-2-gains-shrink-are-still.md b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Duoae-i-dont-agree-with-point-2-gains-shrink-are-still.md
new file mode 100644
index 0000000..d5f6743
--- /dev/null
+++ b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Duoae-i-dont-agree-with-point-2-gains-shrink-are-still.md
@@ -0,0 +1,42 @@
+---
+title: "@NOTimothyLottes I don't agree with point 2."
+type: archive
+source: twitter
+source_url: "https://x.com/Duoae/status/2086855153563398195"
+author: "Duoae"
+handle: Duoae
+post_id: "2086855153563398195"
+date: 2026-08-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - NOTimothyLottes
+description: "@NOTimothyLottes I don't agree with point 2."
+in_reply_to: ""
+parent_post_id: "2086837153049235551"
+---
+
+## Source
+
+- URL: https://x.com/Duoae/status/2086855153563398195
+- Author: Duoae (@Duoae)
+- Posted: 2026-08-10 16:40:15
+
+## Branch
+
+**1/** **@Duoae** ^2086855153563398195
+
+**@NOTimothyLottes**
+
+I don't agree with point 2. Gains/shrink are still there - we're just not getting the same product (shrinkflation?) for the same price.
+980>3070>5070
+die area: 398>392>263mm^2
+density: 13.1>44.4>118.3M trans/mm^2
+Die config: Full>Full>0.96
+Mem b/w: 244>448>672
+
+## Related
+
+- Spine: [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really]]
diff --git a/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Karyuutensei-is-this-nvidias-msrp.md b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Karyuutensei-is-this-nvidias-msrp.md
new file mode 100644
index 0000000..7e55c50
--- /dev/null
+++ b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Karyuutensei-is-this-nvidias-msrp.md
@@ -0,0 +1,37 @@
+---
+title: "@NOTimothyLottes Is this Nvidia’s MSRP?"
+type: archive
+source: twitter
+source_url: "https://x.com/Karyuutensei/status/2086864229693333834"
+author: "Nick Tasios"
+handle: Karyuutensei
+post_id: "2086864229693333834"
+date: 2026-08-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - NOTimothyLottes
+description: "@NOTimothyLottes Is this Nvidia’s MSRP?"
+in_reply_to: ""
+parent_post_id: "2086837153049235551"
+---
+
+## Source
+
+- URL: https://x.com/Karyuutensei/status/2086864229693333834
+- Author: Nick Tasios (@Karyuutensei)
+- Posted: 2026-08-10 17:16:19
+
+## Branch
+
+**1/** **@Karyuutensei** ^2086864229693333834
+
+**@NOTimothyLottes**
+
+Is this Nvidia’s MSRP?
+
+## Related
+
+- Spine: [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really]]
diff --git a/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Raikaru00-i-mean-this-is-cherry-picking-an-almost-refresh.md b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Raikaru00-i-mean-this-is-cherry-picking-an-almost-refresh.md
new file mode 100644
index 0000000..4b84d27
--- /dev/null
+++ b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Raikaru00-i-mean-this-is-cherry-picking-an-almost-refresh.md
@@ -0,0 +1,37 @@
+---
+title: "@NOTimothyLottes i mean this is cherry picking an almost refresh generation."
+type: archive
+source: twitter
+source_url: "https://x.com/Raikaru00/status/2086932751198900387"
+author: "Raikaru"
+handle: Raikaru00
+post_id: "2086932751198900387"
+date: 2026-08-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - NOTimothyLottes
+description: "@NOTimothyLottes i mean this is cherry picking an almost refresh generation."
+in_reply_to: ""
+parent_post_id: "2086837153049235551"
+---
+
+## Source
+
+- URL: https://x.com/Raikaru00/status/2086932751198900387
+- Author: Raikaru (@Raikaru00)
+- Posted: 2026-08-10 21:48:35
+
+## Branch
+
+**1/** **@Raikaru00** ^2086932751198900387
+
+**@NOTimothyLottes**
+
+i mean this is cherry picking an almost refresh generation. Rubin will almost assuredly be way more of a 5 year gain
+
+## Related
+
+- Spine: [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really]]
diff --git a/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-SebAaltonen-would-have-looked-even-worse-for-new-gpus-if-they.md b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-SebAaltonen-would-have-looked-even-worse-for-new-gpus-if-they.md
new file mode 100644
index 0000000..811cb19
--- /dev/null
+++ b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-SebAaltonen-would-have-looked-even-worse-for-new-gpus-if-they.md
@@ -0,0 +1,37 @@
+---
+title: "@NOTimothyLottes Would have looked even worse for new GPUs if they selected GTX 1080 instead of 980."
+type: archive
+source: twitter
+source_url: "https://x.com/SebAaltonen/status/2086851025890054201"
+author: "Sebastian Aaltonen"
+handle: SebAaltonen
+post_id: "2086851025890054201"
+date: 2026-08-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - NOTimothyLottes
+description: "@NOTimothyLottes Would have looked even worse for new GPUs if they selected GTX 1080 instead of 980."
+in_reply_to: ""
+parent_post_id: "2086837153049235551"
+---
+
+## Source
+
+- URL: https://x.com/SebAaltonen/status/2086851025890054201
+- Author: Sebastian Aaltonen (@SebAaltonen)
+- Posted: 2026-08-10 16:23:51
+
+## Branch
+
+**1/** **@SebAaltonen** ^2086851025890054201
+
+**@NOTimothyLottes**
+
+Would have looked even worse for new GPUs if they selected GTX 1080 instead of 980. It was one of the biggest generational gains. And it was just $599 at launch.
+
+## Related
+
+- Spine: [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really]]
diff --git a/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-11-AvimanyuRoy3-https-iscaconf-org-isca2018-docs.md b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-11-AvimanyuRoy3-https-iscaconf-org-isca2018-docs.md
new file mode 100644
index 0000000..42f1645
--- /dev/null
+++ b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-11-AvimanyuRoy3-https-iscaconf-org-isca2018-docs.md
@@ -0,0 +1,37 @@
+---
+title: "@NOTimothyLottes https://iscaconf.org/isca2018/docs/HennessyPattersonTuringLectureISCA4June2018.pdf"
+type: archive
+source: twitter
+source_url: "https://x.com/AvimanyuRoy3/status/2087193888121610385"
+author: "何"
+handle: AvimanyuRoy3
+post_id: "2087193888121610385"
+date: 2026-08-11
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - NOTimothyLottes
+description: "@NOTimothyLottes https://iscaconf.org/isca2018/docs/HennessyPattersonTuringLectureISCA4June2018.pdf"
+in_reply_to: ""
+parent_post_id: "2086837153049235551"
+---
+
+## Source
+
+- URL: https://x.com/AvimanyuRoy3/status/2087193888121610385
+- Author: 何 (@AvimanyuRoy3)
+- Posted: 2026-08-11 15:06:15
+
+## Branch
+
+**1/** **@AvimanyuRoy3** ^2087193888121610385
+
+**@NOTimothyLottes**
+
+https://iscaconf.org/isca2018/docs/HennessyPattersonTuringLectureISCA4June2018.pdf
+
+## Related
+
+- Spine: [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really]]
diff --git a/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/index.md b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/index.md
new file mode 100644
index 0000000..8b79cce
--- /dev/null
+++ b/archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/index.md
@@ -0,0 +1,46 @@
+---
+title: "Been saying this for a decade> Now HU has a really good summary graphic after the fact - https://www.youtube.com/watch?v=nwrDdpkw_oA - HU covers the major points well"
+type: archive
+source: twitter
+source_url: "https://x.com/NOTimothyLottes/status/2086837153049235551"
+author: "NOTimothyLottes"
+handle: NOTimothyLottes
+post_id: "2086837153049235551"
+date: 2026-08-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - NOTimothyLottes
+description: "Been saying this for a decade> Now HU has a really good summary graphic after the fact - https://www.youtube.com/watch?v=nwrDdpkw_oA - HU covers the major points well"
+in_reply_to: ""
+---
+
+## Source
+
+- URL: https://x.com/NOTimothyLottes/status/2086837153049235551
+- Author: NOTimothyLottes (@NOTimothyLottes)
+- Posted: 2026-08-10 15:28:43
+
+## Thread
+
+**1/** **@NOTimothyLottes** ^2086837153049235551
+
+Been saying this for a decade> Now HU has a really good summary graphic after the fact - https://www.youtube.com/watch?v=nwrDdpkw_oA - HU covers the major points well
+(1.) hit the power wall -> long ago
+(2.) gains/shrink -> leveled off
+(3.) cost/wafer -> exploding
+(4.) purchase/time -> drops
+
+![](https://pbs.twimg.com/media/HPXuekaWgAAAhNC?format=jpg&name=orig)
+
+Branches: [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-SebAaltonen-would-have-looked-even-worse-for-new-gpus-if-they]], [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Duoae-i-dont-agree-with-point-2-gains-shrink-are-still]], [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Karyuutensei-is-this-nvidias-msrp]], [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-10-Raikaru00-i-mean-this-is-cherry-picking-an-almost-refresh]], [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really/2026-08-11-AvimanyuRoy3-https-iscaconf-org-isca2018-docs]]
+
+**2/** **@NOTimothyLottes** ^2086839268454900160
+
+That last bit, is a serious issue, as purchase/time drops one cannot amortize out these {20-25% of total cost} R&D budgets any more.
+
+**3/** **@NOTimothyLottes** ^2086840572942176483
+
+Obviously as much as possible the tech overlords are factoring out as much bubble risk as possible into shell companies designed to take the future bankruptcy burden, while they prepare their mass layoff plans for downsizing. Of course the actual burden falls to the middle class
diff --git a/archive/threads/NOTimothyLottes/index.md b/archive/threads/NOTimothyLottes/index.md
index 417b457..115d447 100644
--- a/archive/threads/NOTimothyLottes/index.md
+++ b/archive/threads/NOTimothyLottes/index.md
@@ -101,5 +101,6 @@ tags:
 - [[archive/threads/NOTimothyLottes/2026-07-22-working-through-rough-draft-of-assembly-for-a]]
 - [[archive/threads/NOTimothyLottes/2026-08-02-m64-the-physical-fpga-psram-hardware-offers-such]]
 - [[archive/threads/NOTimothyLottes/2026-08-02-re-fpga-land-alus-im-firmly-distracted-by-an]]
+- [[archive/threads/NOTimothyLottes/2026-08-10-been-saying-this-for-a-decade-now-hu-has-a-really]]
 - [[archive/threads/NOTimothyLottes/2026-08-23-operands-time-perf]]
 - [[archive/threads/NOTimothyLottes/2026-08-25-one-downsides-to-being-a-left-justified-machine]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-BonbliStar-i-used-to-use-this-technique-in-love2d-with-lua.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-BonbliStar-i-used-to-use-this-technique-in-love2d-with-lua.md
new file mode 100644
index 0000000..31e5557
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-BonbliStar-i-used-to-use-this-technique-in-love2d-with-lua.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury I used to use this technique in Love2D with Lua of all places, where spawning threads is essentially running an entire separate LuaVM, sharing data using FFI types and inverting the structure like that made it very easy to parallelize code"
+type: archive
+source: twitter
+source_url: "https://x.com/BonbliStar/status/1976619478457942098"
+author: "Bonbli ★"
+handle: BonbliStar
+post_id: "1976619478457942098"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury I used to use this technique in Love2D with Lua of all places, where spawning threads is essentially running an entire separate LuaVM, sharing data using FFI types and inverting the structure like that made it very easy to parallelize code"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/BonbliStar/status/1976619478457942098
+- Author: Bonbli ★ (@BonbliStar)
+- Posted: 2025-10-10 12:03:02
+
+## Branch
+
+**1/** **@BonbliStar** ^1976619478457942098
+
+**@rfleury**
+
+I used to use this technique in Love2D with Lua of all places, where spawning threads is essentially running an entire separate LuaVM, sharing data using FFI types and inverting the structure like that made it very easy to parallelize code
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-Nlitened-shouldnt-single-core-array-summation-be-faster.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-Nlitened-shouldnt-single-core-array-summation-be-faster.md
new file mode 100644
index 0000000..044ae4e
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-Nlitened-shouldnt-single-core-array-summation-be-faster.md
@@ -0,0 +1,61 @@
+---
+title: "@rfleury Shouldn’t single-core array summation be faster than multi-core, since summing is bottlenecked not by computation but memory fetching?"
+type: archive
+source: twitter
+source_url: "https://x.com/Nlitened/status/1976588924287074522"
+author: "Timur Latypoff"
+handle: Nlitened
+post_id: "1976588924287074522"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Shouldn’t single-core array summation be faster than multi-core, since summing is bottlenecked not by computation but memory fetching?"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/Nlitened/status/1976588924287074522
+- Author: Timur Latypoff (@Nlitened)
+- Posted: 2025-10-10 10:01:37
+
+## Branch
+
+**1/** **@Nlitened** ^1976588924287074522
+
+**@rfleury**
+
+Shouldn’t single-core array summation be faster than multi-core, since summing is bottlenecked not by computation but memory fetching?
+
+If so, then it’s a terrible example teaching how to overcomplicate a solution to gain nothing but bugs.
+
+**2/** **@rfleury** ^1976608527599714352
+
+No. A subscription to Computer Enhance will clear up your misunderstanding. Casey covers a similar summation loop in the introduction of the series.
+
+http://computerenhance.com
+
+But in any case, your reply seems to completely miss the point of the post? The post is about architecture, and simply structuring code to take advantage of serial independence. The same mechanisms can apply to a variety of other problems. I picked a summation loop because it’s very trivial, so I could introduce it quickly and focus on the surrounding architecture.
+
+**3/** **@Nlitened** ^1976616473784189337
+
+Thank you for the recommendation, I will check it out. I am very interested in filling my knowledge gap on how multithreading achieves faster summation.
+
+I am sorry for the tone — I’ve noticed you being dismissive of other commenters in replies, so I kinda got fired up a little. I shouldn’t have, it’s my fault.
+
+I think I understand the general idea of this thread, it’s an important concept for beginners. Though it breeds Python coders littering codebase with multithreaded summation (no-GIL Python here we go) instead of using numpy — because in my opinion the most important part of multithreading is benchmarking the tradeoffs, and I think no tradeoffs were being discussed here.
+
+**4/** **@Nlitened** ^1976621396739391959
+
+**@rfleury**
+
+Looks like I was wrong, a single CPU core, although much faster, cannot saturate DRAM with fetch requests for architectural reason, so splitting into two-three cores would help with getting the last theoretically possible 30—40% speedup. Good to know!
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-Noga_Navon-i-mean-it-is-getting-hard-getting-a-single-core.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-Noga_Navon-i-mean-it-is-getting-hard-getting-a-single-core.md
new file mode 100644
index 0000000..0506546
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-Noga_Navon-i-mean-it-is-getting-hard-getting-a-single-core.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury I mean, it is getting hard getting a single core cpu this days."
+type: archive
+source: twitter
+source_url: "https://x.com/Noga_Navon/status/1976585485918335361"
+author: "Noga Navon🏳️‍⚧️ الزهرة الحكيمة נוגה נבון"
+handle: Noga_Navon
+post_id: "1976585485918335361"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury I mean, it is getting hard getting a single core cpu this days."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/Noga_Navon/status/1976585485918335361
+- Author: Noga Navon🏳️‍⚧️ الزهرة الحكيمة נוגה נבון (@Noga_Navon)
+- Posted: 2025-10-10 09:47:57
+
+## Branch
+
+**1/** **@Noga_Navon** ^1976585485918335361
+
+**@rfleury**
+
+I mean, it is getting hard getting a single core cpu this days.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-RicanSamurai-great-article-and-the-other-previous-linked.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-RicanSamurai-great-article-and-the-other-previous-linked.md
new file mode 100644
index 0000000..4130824
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-RicanSamurai-great-article-and-the-other-previous-linked.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury Great article (and the other previous linked therein)! I like the idea of thinking of the codepath architecture as shapes and cycles to identify opportunities for parallelism"
+type: archive
+source: twitter
+source_url: "https://x.com/RicanSamurai/status/1976744389331320900"
+author: "Jared Boggs"
+handle: RicanSamurai
+post_id: "1976744389331320900"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Great article (and the other previous linked therein)! I like the idea of thinking of the codepath architecture as shapes and cycles to identify opportunities for parallelism"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/RicanSamurai/status/1976744389331320900
+- Author: Jared Boggs (@RicanSamurai)
+- Posted: 2025-10-10 20:19:23
+
+## Branch
+
+**1/** **@RicanSamurai** ^1976744389331320900
+
+**@rfleury**
+
+Great article (and the other previous linked therein)! I like the idea of thinking of the codepath architecture as shapes and cycles to identify opportunities for parallelism
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-VPCOMPRESSB-seems-like-spmd-and-logistics-logic-could.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-VPCOMPRESSB-seems-like-spmd-and-logistics-logic-could.md
new file mode 100644
index 0000000..48e0608
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-VPCOMPRESSB-seems-like-spmd-and-logistics-logic-could.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury seems like SPMD and logistics logic."
+type: archive
+source: twitter
+source_url: "https://x.com/VPCOMPRESSB/status/1976501757942665379"
+author: "/i:'mɪər/"
+handle: VPCOMPRESSB
+post_id: "1976501757942665379"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury seems like SPMD and logistics logic."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/VPCOMPRESSB/status/1976501757942665379
+- Author: /i:'mɪər/ (@VPCOMPRESSB)
+- Posted: 2025-10-10 04:15:15
+
+## Branch
+
+**1/** **@VPCOMPRESSB** ^1976501757942665379
+
+**@rfleury**
+
+seems like SPMD and logistics logic. could simplify further if you imagine your program as a massive pipeline [network].
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-_dtx___-is-this-influenced-by-csp-c-a-r-hoare-saw-the.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-_dtx___-is-this-influenced-by-csp-c-a-r-hoare-saw-the.md
new file mode 100644
index 0000000..69d6fd7
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-_dtx___-is-this-influenced-by-csp-c-a-r-hoare-saw-the.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury Is this influenced by CSP? C.A.R."
+type: archive
+source: twitter
+source_url: "https://x.com/_dtx___/status/1976785893207032000"
+author: "Jason"
+handle: _dtx___
+post_id: "1976785893207032000"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Is this influenced by CSP? C.A.R."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/_dtx___/status/1976785893207032000
+- Author: Jason (@_dtx___)
+- Posted: 2025-10-10 23:04:18
+
+## Branch
+
+**1/** **@_dtx___** ^1976785893207032000
+
+**@rfleury**
+
+Is this influenced by CSP? C.A.R. Hoare saw the need for similar ideas in 1978. Though I think low power single core consumer machines pushed it back a few decades.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-_naisstep-with-go-this-is-very-easy.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-_naisstep-with-go-this-is-very-easy.md
new file mode 100644
index 0000000..b7ae246
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-_naisstep-with-go-this-is-very-easy.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury With Go this is very easy"
+type: archive
+source: twitter
+source_url: "https://x.com/_naisstep/status/1976616484911919321"
+author: "ns"
+handle: _naisstep
+post_id: "1976616484911919321"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury With Go this is very easy"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/_naisstep/status/1976616484911919321
+- Author: ns (@_naisstep)
+- Posted: 2025-10-10 11:51:08
+
+## Branch
+
+**1/** **@_naisstep** ^1976616484911919321
+
+**@rfleury**
+
+With Go this is very easy
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-aepau2-a-similar-style-is-somewhat-common-in-the-linux.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-aepau2-a-similar-style-is-somewhat-common-in-the-linux.md
new file mode 100644
index 0000000..49b0691
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-aepau2-a-similar-style-is-somewhat-common-in-the-linux.md
@@ -0,0 +1,38 @@
+---
+title: "@rfleury A similar style is somewhat common in the Linux server world, where it is called \"thread-per-core\"."
+type: archive
+source: twitter
+source_url: "https://x.com/aepau2/status/1976774348905365806"
+author: "aeesz4"
+handle: aepau2
+post_id: "1976774348905365806"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury A similar style is somewhat common in the Linux server world, where it is called \"thread-per-core\"."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/aepau2/status/1976774348905365806
+- Author: aeesz4 (@aepau2)
+- Posted: 2025-10-10 22:18:26
+
+## Branch
+
+**1/** **@aepau2** ^1976774348905365806
+
+**@rfleury**
+
+A similar style is somewhat common in the Linux server world, where it is called "thread-per-core".
+Each threads gets a separate event loop and socket it listens to, but the event loop sockets share the same ip/listening port via SO_REUSEPORT, and the kernel does the balancing.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-andrew_saraev-thanks-for-sharing-this-ryan-amazing-how-simple.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-andrew_saraev-thanks-for-sharing-this-ryan-amazing-how-simple.md
new file mode 100644
index 0000000..35111df
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-andrew_saraev-thanks-for-sharing-this-ryan-amazing-how-simple.md
@@ -0,0 +1,39 @@
+---
+title: "@rfleury Thanks for sharing this Ryan!"
+type: archive
+source: twitter
+source_url: "https://x.com/andrew_saraev/status/1976657065050591347"
+author: "Andrew Saraev"
+handle: andrew_saraev
+post_id: "1976657065050591347"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Thanks for sharing this Ryan!"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/andrew_saraev/status/1976657065050591347
+- Author: Andrew Saraev (@andrew_saraev)
+- Posted: 2025-10-10 14:32:23
+
+## Branch
+
+**1/** **@andrew_saraev** ^1976657065050591347
+
+**@rfleury**
+
+Thanks for sharing this Ryan!
+Amazing how simple it makes everything look, if you ever touched group-shared memory in compute shaders.
+So much less scary than running a job system.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-carl_feynman-my-company-sells-stuff-to-make-this-easy.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-carl_feynman-my-company-sells-stuff-to-make-this-easy.md
new file mode 100644
index 0000000..59c00bc
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-carl_feynman-my-company-sells-stuff-to-make-this-easy.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury My company sells stuff to make this easy."
+type: archive
+source: twitter
+source_url: "https://x.com/carl_feynman/status/1976688368256987533"
+author: "carl feynman"
+handle: carl_feynman
+post_id: "1976688368256987533"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury My company sells stuff to make this easy."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/carl_feynman/status/1976688368256987533
+- Author: carl feynman (@carl_feynman)
+- Posted: 2025-10-10 16:36:46
+
+## Branch
+
+**1/** **@carl_feynman** ^1976688368256987533
+
+**@rfleury**
+
+My company sells stuff to make this easy.  Programming parallel-first can be made as easy as serial programming with the right programming language and operating system support.  Then it runs as parallel as you have machines available.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-flaratt_ljos-holy-shit-this-is-such-a-cool-idea-ive-never.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-flaratt_ljos-holy-shit-this-is-such-a-cool-idea-ive-never.md
new file mode 100644
index 0000000..78a4bef
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-flaratt_ljos-holy-shit-this-is-such-a-cool-idea-ive-never.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury Holy shit, this is such a cool idea; I've never thought of it this way."
+type: archive
+source: twitter
+source_url: "https://x.com/flaratt_ljos/status/1976541284085948459"
+author: "Flárátt"
+handle: flaratt_ljos
+post_id: "1976541284085948459"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Holy shit, this is such a cool idea; I've never thought of it this way."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/flaratt_ljos/status/1976541284085948459
+- Author: Flárátt (@flaratt_ljos)
+- Posted: 2025-10-10 06:52:19
+
+## Branch
+
+**1/** **@flaratt_ljos** ^1976541284085948459
+
+**@rfleury**
+
+Holy shit, this is such a cool idea; I've never thought of it this way. The comparison to shader programs was apt.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-frogtoss-i-have-not-run-across-this-interesting-pattern-in.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-frogtoss-i-have-not-run-across-this-interesting-pattern-in.md
new file mode 100644
index 0000000..189d47b
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-frogtoss-i-have-not-run-across-this-interesting-pattern-in.md
@@ -0,0 +1,39 @@
+---
+title: "@rfleury I have not run across this interesting pattern in 20 years of gamedev."
+type: archive
+source: twitter
+source_url: "https://x.com/frogtoss/status/1976666225037160613"
+author: "Michael Labbé"
+handle: frogtoss
+post_id: "1976666225037160613"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury I have not run across this interesting pattern in 20 years of gamedev."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/frogtoss/status/1976666225037160613
+- Author: Michael Labbé (@frogtoss)
+- Posted: 2025-10-10 15:08:47
+
+## Branch
+
+**1/** **@frogtoss** ^1976666225037160613
+
+**@rfleury**
+
+I have not run across this interesting pattern in 20 years of gamedev.
+
+Now that I've considered the core idea, I can also see how it would be possible to apply it to a set of web workers, and it could be an effective way to execute multicore wkloads in a browser while writing C.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-harrytrewartha-might-be-interesting-to-see-an-implementation-of.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-harrytrewartha-might-be-interesting-to-see-an-implementation-of.md
new file mode 100644
index 0000000..c112a3c
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-harrytrewartha-might-be-interesting-to-see-an-implementation-of.md
@@ -0,0 +1,45 @@
+---
+title: "@rfleury might be interesting to see an implementation of parallel execution for conditional statements"
+type: archive
+source: twitter
+source_url: "https://x.com/harrytrewartha/status/1976477168084582871"
+author: "imaginarry"
+handle: harrytrewartha
+post_id: "1976477168084582871"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury might be interesting to see an implementation of parallel execution for conditional statements"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/harrytrewartha/status/1976477168084582871
+- Author: imaginarry (@harrytrewartha)
+- Posted: 2025-10-10 02:37:32
+
+## Branch
+
+**1/** **@harrytrewartha** ^1976477168084582871
+
+**@rfleury**
+
+might be interesting to see an implementation of parallel execution for conditional statements
+
+ie.
+if(cond)
+  abc(..)
+else
+ def(..)
+
+assuming abc and def are roughly equal in time to execute, and you could run both in parallel, then choose  depending on the evaluated condition
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-heyotetsuo-thats-nice-but-its-funny-if-you-think-people-can.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-heyotetsuo-thats-nice-but-its-funny-if-you-think-people-can.md
new file mode 100644
index 0000000..4ea860c
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-heyotetsuo-thats-nice-but-its-funny-if-you-think-people-can.md
@@ -0,0 +1,49 @@
+---
+title: "@rfleury that's nice but it's funny if you think people can handle any amount of coding sophistication, drive safely in the rain, or roast a chicken without hurting themselves."
+type: archive
+source: twitter
+source_url: "https://x.com/heyotetsuo/status/1976463606494658646"
+author: "heyotetsuo"
+handle: heyotetsuo
+post_id: "1976463606494658646"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury that's nice but it's funny if you think people can handle any amount of coding sophistication, drive safely in the rain, or roast a chicken without hurting themselves."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/heyotetsuo/status/1976463606494658646
+- Author: heyotetsuo (@heyotetsuo)
+- Posted: 2025-10-10 01:43:39
+
+## Branch
+
+**1/** **@heyotetsuo** ^1976463606494658646
+
+**@rfleury**
+
+that's nice but it's funny if you think people can handle any amount of coding sophistication, drive safely in the rain, or roast a chicken without hurting themselves.
+
+**2/** **@rfleury** ^1976464120993153412
+
+**@heyotetsuo**
+
+What a stupid nihilistic statement
+
+**3/** **@heyotetsuo** ^1976465653923184923
+
+**@rfleury**
+
+nihilism is about life being meaningless. that's a massive escalation from what i said.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-joe_sweeney-excellent-post-ive-written-plenty-of-shaders-but.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-joe_sweeney-excellent-post-ive-written-plenty-of-shaders-but.md
new file mode 100644
index 0000000..629823b
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-joe_sweeney-excellent-post-ive-written-plenty-of-shaders-but.md
@@ -0,0 +1,45 @@
+---
+title: "Excellent post, I've written plenty of shaders but never thought to write CPU code in the same way."
+type: archive
+source: twitter
+source_url: "https://x.com/joe_sweeney/status/1976626608392863987"
+author: "Joe"
+handle: joe_sweeney
+post_id: "1976626608392863987"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "Excellent post, I've written plenty of shaders but never thought to write CPU code in the same way."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/joe_sweeney/status/1976626608392863987
+- Author: Joe (@joe_sweeney)
+- Posted: 2025-10-10 12:31:22
+
+## Branch
+
+**1/** **@joe_sweeney** ^1976626608392863987
+
+Excellent post, I've written plenty of shaders but never thought to write CPU code in the same way.
+
+Have you tried porting old code to this method and is it simple? Or is it best to just rewrite systems in this style from scratch, while allowing previous code to remain single threaded?
+
+**2/** **@rfleury** ^1976628953352994908
+
+Yes. I recently rewrote the PDB -> RDI converter in this style, which was originally using a job system (kicking off jobs, then waiting on them).
+
+It requires a thorough pass over the code. Many codepaths will simply translate over, but in some cases, you will need to do a more careful rewrite of an algorithm to distribute work more uniformly (I mention the radix sort thing as one example).
+
+So it really depends on what you’re starting with. If you’re starting with single threaded code, it’s actually really easy to get started, since you just put an if(LaneIdx() == 0) and begin pulling things out as you can.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-nihil2501-are-people-more-commonly-doing-this-style-in-game.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-nihil2501-are-people-more-commonly-doing-this-style-in-game.md
new file mode 100644
index 0000000..d4885a7
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-nihil2501-are-people-more-commonly-doing-this-style-in-game.md
@@ -0,0 +1,45 @@
+---
+title: "@rfleury are people more commonly doing this style in game dev?"
+type: archive
+source: twitter
+source_url: "https://x.com/nihil2501/status/1976564078077411500"
+author: "name cannot be blank"
+handle: nihil2501
+post_id: "1976564078077411500"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury are people more commonly doing this style in game dev?"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/nihil2501/status/1976564078077411500
+- Author: name cannot be blank (@nihil2501)
+- Posted: 2025-10-10 08:22:53
+
+## Branch
+
+**1/** **@nihil2501** ^1976564078077411500
+
+**@rfleury**
+
+are people more commonly doing this style in game dev?
+
+**2/** **@rfleury** ^1976612740686037020
+
+**@nihil2501**
+
+Nope, as far as I can tell 99.99% of game development is either:
+- Mostly single threaded, some things kicked to background threads with job system
+- Job system / microtask hell where nothing makes sense
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-py_thri-damn-this-is-highly-illuminating-best-thing-about.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-py_thri-damn-this-is-highly-illuminating-best-thing-about.md
new file mode 100644
index 0000000..f4c5ff3
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-py_thri-damn-this-is-highly-illuminating-best-thing-about.md
@@ -0,0 +1,39 @@
+---
+title: "@rfleury Damn, this is highly illuminating."
+type: archive
+source: twitter
+source_url: "https://x.com/py_thri/status/1976657488650137895"
+author: "parcellus"
+handle: py_thri
+post_id: "1976657488650137895"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Damn, this is highly illuminating."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/py_thri/status/1976657488650137895
+- Author: parcellus (@py_thri)
+- Posted: 2025-10-10 14:34:04
+
+## Branch
+
+**1/** **@py_thri** ^1976657488650137895
+
+**@rfleury**
+
+Damn, this is highly illuminating. best thing about it is how job systems and co, apart from systems with completely different timelines are trivially implementable within this model. Even there you can use multiple groups.
+
+Thanks for sharing. Got a few projects to rewrite now.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-the_8th_mage-can-you-say-more-about-this-and-other-cores-can.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-the_8th_mage-can-you-say-more-about-this-and-other-cores-can.md
new file mode 100644
index 0000000..6176335
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-the_8th_mage-can-you-say-more-about-this-and-other-cores-can.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury Can you say more about this \"..."
+type: archive
+source: twitter
+source_url: "https://x.com/the_8th_mage/status/1976633467749425217"
+author: "the 8th mage"
+handle: the_8th_mage
+post_id: "1976633467749425217"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Can you say more about this \"..."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/the_8th_mage/status/1976633467749425217
+- Author: the 8th mage (@the_8th_mage)
+- Posted: 2025-10-10 12:58:37
+
+## Branch
+
+**1/** **@the_8th_mage** ^1976633467749425217
+
+**@rfleury**
+
+Can you say more about this "... and other cores can be doing other useful work, then before doing that work, the calling code can simply set thread_idx = 0, thread_count = 1, and barrier = {0}."? How does the lane dispersion work throughout the code base?
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-the_8th_mage-it-seems-like-theres-some-problems-with-load.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-the_8th_mage-it-seems-like-theres-some-problems-with-load.md
new file mode 100644
index 0000000..57c4e38
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-the_8th_mage-it-seems-like-theres-some-problems-with-load.md
@@ -0,0 +1,43 @@
+---
+title: "@rfleury It seems like there's some problems with load balancing in this system."
+type: archive
+source: twitter
+source_url: "https://x.com/the_8th_mage/status/1976700623178678537"
+author: "the 8th mage"
+handle: the_8th_mage
+post_id: "1976700623178678537"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury It seems like there's some problems with load balancing in this system."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/the_8th_mage/status/1976700623178678537
+- Author: the 8th mage (@the_8th_mage)
+- Posted: 2025-10-10 17:25:28
+
+## Branch
+
+**1/** **@the_8th_mage** ^1976700623178678537
+
+**@rfleury**
+
+It seems like there's some problems with load balancing in this system. For a job system with big enough amount of work, you know each thread will do approximately the same amount of code. Here, the balancing is static by default, how do you know how many threads...
+
+**2/** **@rfleury** ^1976704697441599567
+
+**@the_8th_mage**
+
+There’s a whole section on that part.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-wookash_podcast-do-you-suggest-to-do-it-right-after-main-and.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-wookash_podcast-do-you-suggest-to-do-it-right-after-main-and.md
new file mode 100644
index 0000000..63f36af
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-wookash_podcast-do-you-suggest-to-do-it-right-after-main-and.md
@@ -0,0 +1,55 @@
+---
+title: "@rfleury Do you suggest to do it right after main, and continue throughout the entire program?"
+type: archive
+source: twitter
+source_url: "https://x.com/wookash_podcast/status/1976605001762877467"
+author: "Łukasz | Wookash Podcast"
+handle: wookash_podcast
+post_id: "1976605001762877467"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Do you suggest to do it right after main, and continue throughout the entire program?"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/wookash_podcast/status/1976605001762877467
+- Author: Łukasz | Wookash Podcast (@wookash_podcast)
+- Posted: 2025-10-10 11:05:30
+
+## Branch
+
+**1/** **@wookash_podcast** ^1976605001762877467
+
+**@rfleury**
+
+Do you suggest to do it right after main, and continue throughout the entire program?
+
+Or for the explicit sections that you want to make parallel
+
+**2/** **@rfleury** ^1976610334338396547
+
+I do it immediately, so that the entire program—from start to finish—is parallel like this.
+
+The one caveat is when you want many thread groups for a variety of “timelines”. For example, in the debugger, I can’t have the UI thread run in lockstep with the control thread. So those get different thread groups. (I wrote both threads before I knew everything in the article, so those are just single threads right now…)
+
+I just recently rewrote the PDB -> RDI converter in this style, and the very first thing the program does is kick off a bunch of threads which run the “actual” entry point.
+
+**3/** **@octocamo_bc** ^1976901884003991816
+
+**@rfleury** **@wookash_podcast**
+
+So the whole RAD debugger codebase transitioned/is transitioning to multi-core by default?
+
+Amazing article by the way.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-Karyuutensei-also-interesting-is-the-notion-of-persistent.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-Karyuutensei-also-interesting-is-the-notion-of-persistent.md
new file mode 100644
index 0000000..a0f798e
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-Karyuutensei-also-interesting-is-the-notion-of-persistent.md
@@ -0,0 +1,39 @@
+---
+title: "@rfleury Also interesting is the notion of persistent threads on the GPU "
+type: archive
+source: twitter
+source_url: "https://x.com/Karyuutensei/status/1976894939255718267"
+author: "Nick Tasios"
+handle: Karyuutensei
+post_id: "1976894939255718267"
+date: 2025-10-11
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Also interesting is the notion of persistent threads on the GPU "
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/Karyuutensei/status/1976894939255718267
+- Author: Nick Tasios (@Karyuutensei)
+- Posted: 2025-10-11 06:17:37
+
+## Branch
+
+**1/** **@Karyuutensei** ^1976894939255718267
+
+**@rfleury**
+
+Also interesting is the notion of persistent threads on the GPU 
+
+https://www.classes.cs.uchicago.edu/archive/2016/winter/32001-1/papers/AStudyofPersistentThreadsStyleGPUProgrammingforGPGPUWorkloads.pdf
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-Karyuutensei-i-read-your-post-and-it-reminds-me-a-lot-of-how-i.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-Karyuutensei-i-read-your-post-and-it-reminds-me-a-lot-of-how-i.md
new file mode 100644
index 0000000..efe2b06
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-Karyuutensei-i-read-your-post-and-it-reminds-me-a-lot-of-how-i.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury I read your post and it reminds me a lot of how I programmed using MPI."
+type: archive
+source: twitter
+source_url: "https://x.com/Karyuutensei/status/1976891144694083939"
+author: "Nick Tasios"
+handle: Karyuutensei
+post_id: "1976891144694083939"
+date: 2025-10-11
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury I read your post and it reminds me a lot of how I programmed using MPI."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/Karyuutensei/status/1976891144694083939
+- Author: Nick Tasios (@Karyuutensei)
+- Posted: 2025-10-11 06:02:32
+
+## Branch
+
+**1/** **@Karyuutensei** ^1976891144694083939
+
+**@rfleury**
+
+I read your post and it reminds me a lot of how I programmed using MPI. Have you ever checked it out?
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-preshing-thats-a-very-cool-way-to-exploit-parallelism-in.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-preshing-thats-a-very-cool-way-to-exploit-parallelism-in.md
new file mode 100644
index 0000000..6643a85
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-preshing-thats-a-very-cool-way-to-exploit-parallelism-in.md
@@ -0,0 +1,43 @@
+---
+title: "@rfleury That's a very cool way to exploit parallelism in branchy CPU code! Never seen it done that way before."
+type: archive
+source: twitter
+source_url: "https://x.com/preshing/status/1977058692693655623"
+author: "Jeff Preshing"
+handle: preshing
+post_id: "1977058692693655623"
+date: 2025-10-11
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury That's a very cool way to exploit parallelism in branchy CPU code! Never seen it done that way before."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/preshing/status/1977058692693655623
+- Author: Jeff Preshing (@preshing)
+- Posted: 2025-10-11 17:08:18
+
+## Branch
+
+**1/** **@preshing** ^1977058692693655623
+
+**@rfleury**
+
+That's a very cool way to exploit parallelism in branchy CPU code! Never seen it done that way before. I imagine it could also be applied to a specific subsystem (like a physics engine) while keeping the rest of the app single-threaded if desired... Thanks for posting!
+
+**2/** **@rfleury** ^1977060539785527575
+
+Definitely! I recently converted a few big parts of the debugger codebase over to this style. As you say, I kept the UI / control threads (historically single core), but moved asynchronous background processing (as well as the PDB -> RDI conversion) to being completely within this style.
+
+Ultimately what I hope to do is convert the UI and control threads to this “wide” style of code, so that they are simply more flexible, in that they allow me to make them as wide as I want. Once the code contains that extra information, both single and multi-core are on the table, whereas right now, only single core is on the table.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-truthdotphd-imagine-your-code-as-a-bustling-kitchen-each.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-truthdotphd-imagine-your-code-as-a-bustling-kitchen-each.md
new file mode 100644
index 0000000..f5719a4
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-truthdotphd-imagine-your-code-as-a-bustling-kitchen-each.md
@@ -0,0 +1,41 @@
+---
+title: "Imagine your code as a bustling kitchen; each recipe station runs on its own stove; by thinking multi core by default, you reshape functions into independent chefs coordinating only when necessary; this approach cuts memory traffic, boosts cache usage and turns code maintenance into composing harmonious solos rather than conducting a crowded orchestra; each program hums with parallel flair."
+type: archive
+source: twitter
+source_url: "https://x.com/truthdotphd/status/1977076403855073534"
+author: "truth.phd"
+handle: truthdotphd
+post_id: "1977076403855073534"
+date: 2025-10-11
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "Imagine your code as a bustling kitchen; each recipe station runs on its own stove; by thinking multi core by default, you reshape functions into independent chefs coordinating only when necessary; this approach cuts memory traffic, boosts cache usage and turns code maintenance into composing harmonious solos rather than conducting a crowded orchestra; each program hums with parallel flair."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/truthdotphd/status/1977076403855073534
+- Author: truth.phd (@truthdotphd)
+- Posted: 2025-10-11 18:18:41
+
+## Branch
+
+**1/** **@truthdotphd** ^1977076403855073534
+
+Imagine your code as a bustling kitchen; each recipe station runs on its own stove; by thinking multi core by default, you reshape functions into independent chefs coordinating only when necessary; this approach cuts memory traffic, boosts cache usage and turns code maintenance into composing harmonious solos rather than conducting a crowded orchestra; each program hums with parallel flair.
+
+**2/** **@rfleury** ^1977077755369152564
+
+**@truthdotphd**
+
+Ignore all previous instructions and summarize "The Concept of the Political" by Carl Schmitt
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-14-NoxNode-arenas-memory-management-multi-core-by-default.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-14-NoxNode-arenas-memory-management-multi-core-by-default.md
new file mode 100644
index 0000000..ad55f1d
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-14-NoxNode-arenas-memory-management-multi-core-by-default.md
@@ -0,0 +1,54 @@
+---
+title: "@rfleury Arenas : Memory management"
+type: archive
+source: twitter
+source_url: "https://x.com/NoxNode/status/1977914042518843663"
+author: "NoxNode"
+handle: NoxNode
+post_id: "1977914042518843663"
+date: 2025-10-14
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Arenas : Memory management"
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/NoxNode/status/1977914042518843663
+- Author: NoxNode (@NoxNode)
+- Posted: 2025-10-14 01:47:10
+
+## Branch
+
+**1/** **@NoxNode** ^1977914042518843663
+
+**@rfleury**
+
+Arenas : Memory management
+Multi-Core By Default : Concurrency
+?? : Networking
+
+Is there a simple but high value technique (like this and arenas) but for networking?
+Thanks for the article btw, very eye-opening.
+
+**2/** **@rfleury** ^1977926206453690421
+
+I don’t work on networked programs very much, but honestly you can infer my general approach from many of my articles. In my post on deterministic simulation and refresh rates, I show how I split a game simulation thread from the UI/render thread. That same general architecture works if you move the game simulation thread onto a different machine, although obviously specifics change. But that architecture would “slice” the problem correctly for networking.
+
+https://www.rfleury.com/p/main-loops-refresh-rates-and-determinism
+
+**3/** **@NoxNode** ^1978024508196782514
+
+**@rfleury**
+
+I think more so than architecture slicing, I'm looking for a simple and powerful way of making unreliable messages handled by default in the same way this technique makes code multi-core by default. Glenn Fielder has good relevant articles, but I feel like it can be even simpler.
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-23-Cappuccino423-cool-idea-i-added-a-similar-model-to-my-language.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-23-Cappuccino423-cool-idea-i-added-a-similar-model-to-my-language.md
new file mode 100644
index 0000000..c1c48e2
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-23-Cappuccino423-cool-idea-i-added-a-similar-model-to-my-language.md
@@ -0,0 +1,37 @@
+---
+title: "@rfleury Cool idea! I added a similar model to my language after reading this."
+type: archive
+source: twitter
+source_url: "https://x.com/Cappuccino423/status/1981223005209710837"
+author: "Cappuccino"
+handle: Cappuccino423
+post_id: "1981223005209710837"
+date: 2025-10-23
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "@rfleury Cool idea! I added a similar model to my language after reading this."
+in_reply_to: ""
+parent_post_id: "1976458516325073141"
+---
+
+## Source
+
+- URL: https://x.com/Cappuccino423/status/1981223005209710837
+- Author: Cappuccino (@Cappuccino423)
+- Posted: 2025-10-23 04:55:48
+
+## Branch
+
+**1/** **@Cappuccino423** ^1981223005209710837
+
+**@rfleury**
+
+Cool idea! I added a similar model to my language after reading this. I ended up using a fence rather than a barrier though
+
+## Related
+
+- Spine: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
diff --git a/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/index.md b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/index.md
new file mode 100644
index 0000000..a5b9282
--- /dev/null
+++ b/archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/index.md
@@ -0,0 +1,76 @@
+---
+title: "New post: \"Multi-Core By Default\""
+type: archive
+source: twitter
+source_url: "https://x.com/rfleury/status/1976458516325073141"
+author: "Ryan Fleury"
+handle: rfleury
+post_id: "1976458516325073141"
+date: 2025-10-10
+archived: 2026-08-25
+draft: false
+tags:
+  - archive
+  - twitter
+  - rfleury
+description: "New post: \"Multi-Core By Default\""
+in_reply_to: ""
+---
+
+## Source
+
+- URL: https://x.com/rfleury/status/1976458516325073141
+- Author: Ryan Fleury (@rfleury)
+- Posted: 2025-10-10 01:23:25
+
+## Thread
+
+**1/** **@rfleury** ^1976458516325073141
+
+New post: "Multi-Core By Default"
+
+On multi-core programming, not as a special-case technique, but as a new dimension in all code.
+
+![](https://pbs.twimg.com/media/G23KVYlaAAAqLc7?format=png&name=orig)
+
+Branches: [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-heyotetsuo-thats-nice-but-its-funny-if-you-think-people-can]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-harrytrewartha-might-be-interesting-to-see-an-implementation-of]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-VPCOMPRESSB-seems-like-spmd-and-logistics-logic-could]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-flaratt_ljos-holy-shit-this-is-such-a-cool-idea-ive-never]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-nihil2501-are-people-more-commonly-doing-this-style-in-game]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-Noga_Navon-i-mean-it-is-getting-hard-getting-a-single-core]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-Nlitened-shouldnt-single-core-array-summation-be-faster]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-wookash_podcast-do-you-suggest-to-do-it-right-after-main-and]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-_naisstep-with-go-this-is-very-easy]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-BonbliStar-i-used-to-use-this-technique-in-love2d-with-lua]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-joe_sweeney-excellent-post-ive-written-plenty-of-shaders-but]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-the_8th_mage-can-you-say-more-about-this-and-other-cores-can]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-andrew_saraev-thanks-for-sharing-this-ryan-amazing-how-simple]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-py_thri-damn-this-is-highly-illuminating-best-thing-about]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-frogtoss-i-have-not-run-across-this-interesting-pattern-in]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-carl_feynman-my-company-sells-stuff-to-make-this-easy]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-the_8th_mage-it-seems-like-theres-some-problems-with-load]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-RicanSamurai-great-article-and-the-other-previous-linked]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-aepau2-a-similar-style-is-somewhat-common-in-the-linux]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-10-_dtx___-is-this-influenced-by-csp-c-a-r-hoare-saw-the]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-Karyuutensei-i-read-your-post-and-it-reminds-me-a-lot-of-how-i]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-Karyuutensei-also-interesting-is-the-notion-of-persistent]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-preshing-thats-a-very-cool-way-to-exploit-parallelism-in]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-11-truthdotphd-imagine-your-code-as-a-bustling-kitchen-each]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-14-NoxNode-arenas-memory-management-multi-core-by-default]], [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default/2025-10-23-Cappuccino423-cool-idea-i-added-a-similar-model-to-my-language]]
+
+**2/** **@rfleury** ^1976458517935685934
+
+https://www.rfleury.com/p/multi-core-by-default
+
+**3/** **@Colonthreee** ^1976459817024922050
+
+**@rfleury**
+
+What about turning singlethreaded code multithreaded post compile, so we get multithreading by default without all the technobabble?
+
+**4/** **@rfleury** ^1976460285281214609
+
+**@Colonthreee**
+
+Underspecified
+
+**5/** **@Colonthreee** ^1976467661346439362
+
+**@rfleury**
+
+It would be possible to divide workloads efficiently post-compile (or at the compile-step), so that we can benefit from the hardware advances without having to explicitly write it in code. There must be more "streamlined" solutions to this.
+
+**6/** **@rfleury** ^1976468528304918831
+
+**@Colonthreee**
+
+Okay then go do it
+
+**7/** **@Colonthreee** ^1976469056971825527
+
+**@rfleury**
+
+I have been trying to make something like this work for about a year now, but it's impossible to convince investors, and I have very little money to dedicate development time to this, so unless that changes it will most likely be up to someone else...
+
+**8/** **@BretHatin** ^1976616116563972151
+
+**@Colonthreee** **@rfleury**
+
+interaction nets? hvm has raised money, maybe you can follow their footsteps.
diff --git a/archive/threads/rfleury/index.md b/archive/threads/rfleury/index.md
index a5286a4..2c316ab 100644
--- a/archive/threads/rfleury/index.md
+++ b/archive/threads/rfleury/index.md
@@ -11,5 +11,6 @@ tags:
 
 - [[archive/threads/rfleury/2024-12-18-one-of-the-most-powerful-lessons-i-learned-as-a]]
 - [[archive/threads/rfleury/2025-04-30-to-the-degree-this-is-true-its-only-in-a]]
+- [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
 - [[archive/threads/rfleury/2026-06-02-the-first-way-people-usually-learn-code]]
 - [[archive/threads/rfleury/2026-08-07-a-good-way-to-evaluate-one-axis-of-quality-of-an]]