<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #async</title>
    <link>/tags/async/</link>
    <description>Recent bookmarks tagged #async</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:52 +0000</lastBuildDate>
    <item>
      <title>Playground Wisdom: Threads Beat Async/Await | Armin Ronacher&#39;s Thoughts and Writings</title>
      <link>https://lucumr.pocoo.org/2024/11/18/threads-beat-async-await/</link>
      <description>It&#39;s been a few years since I wrote about my challenges with async/await-based systems and how they just seem to not support back pressure well. A few years later, I do not think that this problem has subsided much, but my thinking and understanding have perhaps evolved a bit. I&#39;m now convinced that async/await is, in fact, a bad abstraction for most languages, and we should be aiming for something better instead and that I believe to be thread.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #async #programming #python #threads&lt;/p&gt;</description>
      <pubDate>Tue, 19 Nov 2024 20:23:52 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29857</guid>
      <category>async</category>
      <category>programming</category>
      <category>python</category>
      <category>threads</category>
    </item>
    <item>
      <title>Pin and suffering</title>
      <link>https://fasterthanli.me/articles/pin-and-suffering</link>
      <description>I&#39;d like to think that my understanding of &#34;async Rust&#34; has increased over the past year or so. I&#39;m 100% onboard with the basic principle: I would like to handle thousands of concurrent tasks using a handful of threads. That sounds great!&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #async #concurrency #imported:pinboard #programming #rust&lt;/p&gt;</description>
      <pubDate>Sun, 23 Jul 2023 20:22:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:39</guid>
      <category>async</category>
      <category>concurrency</category>
      <category>imported:pinboard</category>
      <category>programming</category>
      <category>rust</category>
      <enclosure url="https://links.lmorchard.com/static/38c750b3164a126658cd9534659d889b.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>goodeggs/fibrous</title>
      <link>https://github.com/goodeggs/fibrous</link>
      <description>Easily mix asynchronous and synchronous programming styles in node.js&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #async #dev #fibers #imported:pinboard #nodejs #sync #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 25 May 2012 15:10:28 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21884</guid>
      <category>async</category>
      <category>dev</category>
      <category>fibers</category>
      <category>imported:pinboard</category>
      <category>nodejs</category>
      <category>sync</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Simon Wistow - Standing in Line</title>
      <link>http://deflatermouse.livejournal.com/145533.html</link>
      <description>&#34;What I actually want out of this is a kind of de facto standard like Memcached or Apache or whatever that&#39;s so simple to understand and use that it changes the way people develop their apps such that they just start with the assumption that some of their&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #async #caching #queues #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 19 Mar 2008 23:06:33 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:10533</guid>
      <category>async</category>
      <category>caching</category>
      <category>queues</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
