<?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"
	>
<channel>
	<title>Comments on: LabVIEW, at 21, shows a lot of maturity</title>
	<atom:link href="http://thinkinging.com/2007/04/07/labview-at-21-shows-a-lot-of-maturity/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkinging.com/2007/04/07/labview-at-21-shows-a-lot-of-maturity/</link>
	<description>an unfiltered stream of data flow consciousness</description>
	<pubDate>Tue,  7 Oct 2008 04:14:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Jim Kring</title>
		<link>http://thinkinging.com/2007/04/07/labview-at-21-shows-a-lot-of-maturity/#comment-223</link>
		<dc:creator>Jim Kring</dc:creator>
		<pubDate>Thu, 12 Apr 2007 14:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2007/04/07/labview-at-21-shows-a-lot-of-maturity/#comment-223</guid>
		<description>Hi, Carsten. Yes, I agree that there needs to be more work done by NI to list known bugs.  But, they're moving in the right direction ;)</description>
		<content:encoded><![CDATA[<p>Hi, Carsten. Yes, I agree that there needs to be more work done by NI to list known bugs.  But, they&#8217;re moving in the right direction <img src='http://thinkinging.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carsten</title>
		<link>http://thinkinging.com/2007/04/07/labview-at-21-shows-a-lot-of-maturity/#comment-222</link>
		<dc:creator>Carsten</dc:creator>
		<pubDate>Thu, 12 Apr 2007 12:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2007/04/07/labview-at-21-shows-a-lot-of-maturity/#comment-222</guid>
		<description>One thing I'm still missing though, is a list of &lt;em&gt;currently known&lt;/em&gt; bugs!   Not just the "small" list of known problems they publish.

But unfortunately just publishing fixed bugs and admitting some known problems (they'll hit the forums soon anyway) doesn't make a high-quality software. IMO NI has really to work here. NI often introduced very new features with many bugs that were really trouble makers. That happend for LV 7 (which was very stable and usuable with 7.1.1) as well as for LV 8.</description>
		<content:encoded><![CDATA[<p>One thing I&#8217;m still missing though, is a list of <em>currently known</em> bugs!   Not just the &#8220;small&#8221; list of known problems they publish.</p>
<p>But unfortunately just publishing fixed bugs and admitting some known problems (they&#8217;ll hit the forums soon anyway) doesn&#8217;t make a high-quality software. IMO NI has really to work here. NI often introduced very new features with many bugs that were really trouble makers. That happend for LV 7 (which was very stable and usuable with 7.1.1) as well as for LV 8.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Maila</title>
		<link>http://thinkinging.com/2007/04/07/labview-at-21-shows-a-lot-of-maturity/#comment-216</link>
		<dc:creator>Tomi Maila</dc:creator>
		<pubDate>Sun, 08 Apr 2007 12:13:38 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2007/04/07/labview-at-21-shows-a-lot-of-maturity/#comment-216</guid>
		<description>I fully agree with you Jim that both making the bug fixes public and having full installer instead of a patch are a great leap towards the right direction of appreciating professional software developers. Great work NI.

&lt;a href="http://expressionflow.com" title="EXPRESSIONFLOW - A blog on LabVIEW and visual object-oriented programming" rel="nofollow"&gt;-= EXPRESSIONFLOW =-&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I fully agree with you Jim that both making the bug fixes public and having full installer instead of a patch are a great leap towards the right direction of appreciating professional software developers. Great work NI.</p>
<p><a href="http://expressionflow.com" title="EXPRESSIONFLOW - A blog on LabVIEW and visual object-oriented programming" rel="nofollow">-= EXPRESSIONFLOW =-</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
