<?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 2014/02/09	</title>
	<atom:link href="https://www.dragonflydigest.com/2014/02/09/lazy-reading-for-20140209/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2014/02/09/lazy-reading-for-20140209/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Mon, 10 Feb 2014 05:27:01 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.1</generator>
	<item>
		<title>
		By: Justin Sherrill		</title>
		<link>https://www.dragonflydigest.com/2014/02/09/lazy-reading-for-20140209/comment-page-1/#comment-79685</link>

		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Mon, 10 Feb 2014 05:27:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13293#comment-79685</guid>

					<description><![CDATA[Yeah, I know the dangers, but still: at least read-only notifications would be nice.  I have a building generator that, if something goes wrong, lights up a little red light on a box in the building basement.  There&#039;s no other option, according to the people that installed it.  That&#039;s dumb.

A lot of people don&#039;t understand that being conservative with change doesn&#039;t always mean less errors; it means old problems stick around forever.  Net result is the same number of issues.  That&#039;s a general response to a specific question, but the principle holds.]]></description>
			<content:encoded><![CDATA[<p>Yeah, I know the dangers, but still: at least read-only notifications would be nice.  I have a building generator that, if something goes wrong, lights up a little red light on a box in the building basement.  There&#8217;s no other option, according to the people that installed it.  That&#8217;s dumb.</p>
<p>A lot of people don&#8217;t understand that being conservative with change doesn&#8217;t always mean less errors; it means old problems stick around forever.  Net result is the same number of issues.  That&#8217;s a general response to a specific question, but the principle holds.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: C2		</title>
		<link>https://www.dragonflydigest.com/2014/02/09/lazy-reading-for-20140209/comment-page-1/#comment-79683</link>

		<dc:creator><![CDATA[C2]]></dc:creator>
		<pubDate>Mon, 10 Feb 2014 04:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13293#comment-79683</guid>

					<description><![CDATA[Ha. I&#039;ll take Modbus most days over some more modern alternatives (I&#039;m looking at you, OPC).

Many of those things aren&#039;t &quot;wired&quot; (more accurately, IP networked) because the risks of doing so outweigh the benefits, at least in the &quot;industrial&quot; realm I work in (admittedly more critical/higher consequences than your average building HVAC). Even in the HVAC business, there has to be some incentive; network interfaces, like variable-frequency motor drives, cost money.

And the industrial realm is a conservative place. Vendors have been hawking digital fieldbuses for years, yet 4-20mA current loop still rules. Wireless standards (ISA S100, WirelessHART) have come on the scene, and while they are used in edge cases where wiring is impractical, you don&#039;t see very many people running an entire plant on them. Simplicity and robustness are still paramount.]]></description>
			<content:encoded><![CDATA[<p>Ha. I&#8217;ll take Modbus most days over some more modern alternatives (I&#8217;m looking at you, OPC).</p>
<p>Many of those things aren&#8217;t &#8220;wired&#8221; (more accurately, IP networked) because the risks of doing so outweigh the benefits, at least in the &#8220;industrial&#8221; realm I work in (admittedly more critical/higher consequences than your average building HVAC). Even in the HVAC business, there has to be some incentive; network interfaces, like variable-frequency motor drives, cost money.</p>
<p>And the industrial realm is a conservative place. Vendors have been hawking digital fieldbuses for years, yet 4-20mA current loop still rules. Wireless standards (ISA S100, WirelessHART) have come on the scene, and while they are used in edge cases where wiring is impractical, you don&#8217;t see very many people running an entire plant on them. Simplicity and robustness are still paramount.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
