<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Lazy Reading for 2016/01/03	</title>
	<atom:link href="https://www.dragonflydigest.com/2016/01/03/lazy-reading-for-20160103/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2016/01/03/lazy-reading-for-20160103/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Mon, 04 Jan 2016 11:26:57 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: czarkoff		</title>
		<link>https://www.dragonflydigest.com/2016/01/03/lazy-reading-for-20160103/comment-page-1/#comment-356724</link>

		<dc:creator><![CDATA[czarkoff]]></dc:creator>
		<pubDate>Mon, 04 Jan 2016 11:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.dragonflydigest.com/?p=17406#comment-356724</guid>

					<description><![CDATA[Re Structural Logging: I can&#039;t help but notice a common trend to turn everything into small payloads with huge amount of metadata. I see no technical merit behind this approach: when string has well-defined carefully engineered format, it can be parsed much more efficiently then JSON data.]]></description>
			<content:encoded><![CDATA[<p>Re Structural Logging: I can&#8217;t help but notice a common trend to turn everything into small payloads with huge amount of metadata. I see no technical merit behind this approach: when string has well-defined carefully engineered format, it can be parsed much more efficiently then JSON data.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
