<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Sync on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/sync/</link>
    <description>Recent content in Sync on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Aug 2019 10:22:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/sync/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Channels vs Mutexes: When to Use Which in Go</title>
      <link>https://blog.turboawesome.win/2019/08/channels-vs-mutexes-when-to-use-which-in-go/</link>
      <pubDate>Wed, 07 Aug 2019 10:22:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2019/08/channels-vs-mutexes-when-to-use-which-in-go/</guid>
      <description>Go&amp;#39;s concurrency slogan is &amp;#39;share memory by communicating.&amp;#39; It&amp;#39;s good advice but incomplete. Some problems are better solved with a mutex than a channel. A decision framework with concrete examples.</description>
    </item>
  </channel>
</rss>
