<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>~ngp</title>
    <link>https://relvokcor.xyz/~ngp/blob/</link>
    <description>Recent content on ~ngp</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Oct 2019 22:25:31 -0600</lastBuildDate>
    
	<atom:link href="https://relvokcor.xyz/~ngp/blob/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>goalpost</title>
      <link>https://relvokcor.xyz/~ngp/blob/posts/goalpost/</link>
      <pubDate>Fri, 11 Oct 2019 22:25:31 -0600</pubDate>
      
      <guid>https://relvokcor.xyz/~ngp/blob/posts/goalpost/</guid>
      <description>a durable, embeddable, worker queue for golang One thing that has always stuck out to me about the Go programming language is it&amp;rsquo;s incredibly strong concurrency model. Go is aggressively simple as a language, and it&amp;rsquo;s asynchronous architecture is no different. Channels are a beautiful implementation of a buffered FIFO queue which have an infinite number of applications. There&amp;rsquo;s no Thread classes, just a simple go in front of a function call.</description>
    </item>
    
  </channel>
</rss>