<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom">
  <title>Planet Golang</title>
  <id>https://planetgolang.dev</id>
  <updated>2026-08-11T06:00:58Z</updated>
  <subtitle>An unopinionated collection of newest Golang articles from all around the web.</subtitle>
  <link href="https://planetgolang.dev"></link>
  <author>
    <name>Tomas Urbanec</name>
    <email>hi@planetgolang.dev</email>
  </author>
  <entry>
    <title>Reading List</title>
    <updated>2026-08-11T01:44:07Z</updated>
    <id>tag:pliutau.com,2026-08-11:/reading-list/</id>
    <link href="https://pliutau.com/reading-list/" rel="alternate"></link>
    <summary type="html">This page is auto-generated from Github Actions workflow that runs every day at night and fetches the 5 latest articles from each of my favorite blogs.</summary>
  </entry>
  <entry>
    <title>Yzma</title>
    <updated>2026-08-10T07:00:00Z</updated>
    <id>tag:internals-for-interns.com,2026-08-10:/posts/yzma/</id>
    <link href="https://internals-for-interns.com/posts/yzma/" rel="alternate"></link>
    <summary type="html">In the previous article&#xA; we looked at what inference actually is — how a model takes a prompt and builds a response one token at a time. I mentioned two Go projects that let you run that loop locally: yzma, which lets Go call the llama.cpp inference engine directly, and kronk,...</summary>
  </entry>
  <entry>
    <title>Some ways to navigate through &#39;git blame&#39; over time in GNU Emacs</title>
    <updated>2026-08-07T02:44:49Z</updated>
    <id>tag:utcc.utoronto.ca,2026-08-07:/~cks/space/blog/programming/EmacsGitBlameOverTime</id>
    <link href="https://utcc.utoronto.ca/~cks/space/blog/programming/EmacsGitBlameOverTime" rel="alternate"></link>
    <summary type="html"></summary>
    <author>
      <name>cks</name>
    </author>
  </entry>
  <entry>
    <title>An interactive tour of Go 1.27</title>
    <updated>2026-08-07T00:00:00Z</updated>
    <id>tag:golangweekly.com,2026-08-07:/issues/613</id>
    <link href="https://golangweekly.com/issues/613" rel="alternate"></link>
    <summary type="html">#​613 — August 7, 2026&#xA;Read the Web Version&#xA;&#xA;&#xA;&#xA;    &#xA;    Go Weekly&#xA;&#xA;  &#xA;&#xA;&#xA;&#xA;  &#xA;  An Interactive Tour of Go 1.27 — Anton Zhiyanov made interactive tours for Go 1.22 through 1.26 but decided to stop. Jesús Espino has picked up the baton and tackles Go 1.27&#39;s hu...</summary>
  </entry>
  <entry>
    <title>Looking at the memory map of a Go 1.27 program on Linux</title>
    <updated>2026-08-06T02:46:15Z</updated>
    <id>tag:utcc.utoronto.ca,2026-08-06:/~cks/space/blog/programming/GoProgramMemoryUseII</id>
    <link href="https://utcc.utoronto.ca/~cks/space/blog/programming/GoProgramMemoryUseII" rel="alternate"></link>
    <summary type="html"></summary>
    <author>
      <name>cks</name>
    </author>
  </entry>
  <entry>
    <title>Writing code isn&#39;t the bottleneck anymore, reading is</title>
    <updated>2026-08-05T22:00:00Z</updated>
    <id>tag:threedots.tech,2026-08-05:/post/understanding-code-is-bottleneck/</id>
    <link href="https://threedots.tech/post/understanding-code-is-bottleneck/" rel="alternate"></link>
    <summary type="html">This week I was working on one non-critical feature that seemed simple at first sight.&#xA;50k lines of code later, it seemed to work as expected.&#xA;In a side project, or a service where &amp;ldquo;nobody will be upset if it&amp;rsquo;s dead and kills everything around&amp;rdquo;, it would be read...</summary>
  </entry>
  <entry>
    <title>Code like a pirate with AI</title>
    <updated>2026-08-04T15:10:00Z</updated>
    <id>tag:bitfieldconsulting.com,2026-08-04:/posts/code-like-pirate</id>
    <link href="https://bitfieldconsulting.com/posts/code-like-pirate" rel="alternate"></link>
    <summary type="html">Will AI coding agents pirate all our jobs? Not if we take back control, &#xD;&#xA;using my six-step PIRATE workflow for shipboard discipline.</summary>
    <author>
      <name>John Arundel</name>
    </author>
  </entry>
  <entry>
    <title>Relative velocity and closing speed</title>
    <updated>2026-08-04T03:01:00Z</updated>
    <id>tag:eli.thegreenplace.net,2026-08-04:/2026/relative-velocity-and-closing-speed/</id>
    <link href="https://eli.thegreenplace.net/2026/relative-velocity-and-closing-speed/" rel="alternate"></link>
    <summary type="html">In Physics simulations or game engines it’s sometimes useful to&#xA;determine the speed with which two objects are approaching each other.&#xA;This post will discuss the concept of closing speed, which is the&#xA;normal component of the relative velocity of two objects.&#xA;&#xA;Relative velocity...</summary>
    <author>
      <name>Eli Bendersky</name>
    </author>
  </entry>
  <entry>
    <title>What &#39;&lt;code&gt;sh -x&lt;/code&gt;&#39; mostly doesn&#39;t tell you about a shell script</title>
    <updated>2026-08-04T02:08:46Z</updated>
    <id>tag:utcc.utoronto.ca,2026-08-04:/~cks/space/blog/programming/ShXWhatYouMiss</id>
    <link href="https://utcc.utoronto.ca/~cks/space/blog/programming/ShXWhatYouMiss" rel="alternate"></link>
    <summary type="html"></summary>
    <author>
      <name>cks</name>
    </author>
  </entry>
  <entry>
    <title>Fake Clocks, Real Guarantees: Inside Go&#39;s synctest</title>
    <updated>2026-08-03T07:00:00Z</updated>
    <id>tag:internals-for-interns.com,2026-08-03:/posts/inside-go-synctest/</id>
    <link href="https://internals-for-interns.com/posts/inside-go-synctest/" rel="alternate"></link>
    <summary type="html">The first time I reached for testing/synctest, I assumed it was a sleep helper with better manners. The public API is small enough to support that assumption:&#xA;synctest.Test(t, func(t *testing.T) { ... })&#xA;synctest.Wait()&#xA;synctest.Sleep(d) // new in Go 1.27&#xA;Three functions, one obv...</summary>
  </entry>
</feed>