<?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: Trusting Autodesk? Contemplating a new product</title>
	<atom:link href="http://www.blog.cadnauseam.com/2009/09/30/trusting-autodesk-contemplating-a-new-product/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blog.cadnauseam.com/2009/09/30/trusting-autodesk-contemplating-a-new-product/</link>
	<description>A strange mix of AutoCAD, music, image manipulation and video</description>
	<lastBuildDate>Thu, 18 Mar 2010 15:32:46 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: José</title>
		<link>http://www.blog.cadnauseam.com/2009/09/30/trusting-autodesk-contemplating-a-new-product/#comment-4062</link>
		<dc:creator>José</dc:creator>
		<pubDate>Sun, 22 Nov 2009 23:59:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.cadnauseam.com/?p=698#comment-4062</guid>
		<description>I don&#039;t trust Autodesk. I think AutoCAD is the worst software I&#039;ve ever used.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t trust Autodesk. I think AutoCAD is the worst software I&#8217;ve ever used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R. Paul Waddington</title>
		<link>http://www.blog.cadnauseam.com/2009/09/30/trusting-autodesk-contemplating-a-new-product/#comment-3995</link>
		<dc:creator>R. Paul Waddington</dc:creator>
		<pubDate>Wed, 30 Sep 2009 22:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.cadnauseam.com/?p=698#comment-3995</guid>
		<description>When marketing drivers development there will always be an issue relating to the longevity of products and trust. Consumable marketeers’ rely on people getting tired of their ‘new’ product but when it come to design and draughting tools – these are not consumables and need to stay put for much longer than most companies have proven willing or able to cope with.

Wm. J. Townsend hit the nail squarely and, if you look closely into what he outlines.  Compare the reality – in relation to the development of MDT/Inventor and Mechanical - with the marketeers’ comments relating to product development, maintenance and life and you will very quickly conclude if you are going to trust Autodesk, it is for reasons other than their history.

It is well past time for consumers and users of software tools to take a more professional approach seeking assurances, from companies like Autodesk, in relation to their products ‘performance’ they can and will be held accountable for, in a tangible manner.  Only when this happens will products of this type, and their developers (Autodesk), garner the level of trust that should exist.</description>
		<content:encoded><![CDATA[<p>When marketing drivers development there will always be an issue relating to the longevity of products and trust. Consumable marketeers’ rely on people getting tired of their ‘new’ product but when it come to design and draughting tools – these are not consumables and need to stay put for much longer than most companies have proven willing or able to cope with.</p>
<p>Wm. J. Townsend hit the nail squarely and, if you look closely into what he outlines.  Compare the reality – in relation to the development of MDT/Inventor and Mechanical &#8211; with the marketeers’ comments relating to product development, maintenance and life and you will very quickly conclude if you are going to trust Autodesk, it is for reasons other than their history.</p>
<p>It is well past time for consumers and users of software tools to take a more professional approach seeking assurances, from companies like Autodesk, in relation to their products ‘performance’ they can and will be held accountable for, in a tangible manner.  Only when this happens will products of this type, and their developers (Autodesk), garner the level of trust that should exist.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kozina</title>
		<link>http://www.blog.cadnauseam.com/2009/09/30/trusting-autodesk-contemplating-a-new-product/#comment-3994</link>
		<dc:creator>David Kozina</dc:creator>
		<pubDate>Wed, 30 Sep 2009 14:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.cadnauseam.com/?p=698#comment-3994</guid>
		<description>A few years ago, I read the book &quot;Dark Ages II: When the Digital Data Die&quot;, by Bryan Bergeron.

If you haven&#039;t already read it, you might find it a good read.  And yes, kind of scary, too.  It would seem to relate to many of the issues you raise.  One of the things I found fascinating was how much faith we currently place on time-UNTESTED storage equipment.  While many archives exist containing many centuries old paper/parchment documents, electronic archives are only decades old at most.  Is it logical to rely so heavily on them?  Yet, what other choices do we have?

http://www.amazon.com/Dark-Ages-II-When-Digital/dp/0130661074/ref=sr_1_5?ie=UTF8&amp;s=books&amp;qid=1254321002&amp;sr=1-5</description>
		<content:encoded><![CDATA[<p>A few years ago, I read the book &#8220;Dark Ages II: When the Digital Data Die&#8221;, by Bryan Bergeron.</p>
<p>If you haven&#8217;t already read it, you might find it a good read.  And yes, kind of scary, too.  It would seem to relate to many of the issues you raise.  One of the things I found fascinating was how much faith we currently place on time-UNTESTED storage equipment.  While many archives exist containing many centuries old paper/parchment documents, electronic archives are only decades old at most.  Is it logical to rely so heavily on them?  Yet, what other choices do we have?</p>
<p><a href="http://www.amazon.com/Dark-Ages-II-When-Digital/dp/0130661074/ref=sr_1_5?ie=UTF8&amp;s=books&amp;qid=1254321002&amp;sr=1-5" rel="nofollow">http://www.amazon.com/Dark-Ages-II-When-Digital/dp/0130661074/ref=sr_1_5?ie=UTF8&amp;s=books&amp;qid=1254321002&amp;sr=1-5</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ralphg</title>
		<link>http://www.blog.cadnauseam.com/2009/09/30/trusting-autodesk-contemplating-a-new-product/#comment-3993</link>
		<dc:creator>ralphg</dc:creator>
		<pubDate>Wed, 30 Sep 2009 13:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.cadnauseam.com/?p=698#comment-3993</guid>
		<description>I s&#039;pose you could ask the same of any other related product. Fer instance, this press release headline of yesterday:

&quot;COADE releases CADWorx P&amp;ID Professional 2010 for process and instrumentation diagrams with support for AutoCAD 2010 plus other enhancements&quot;

All your questions can be boiled down to one: &quot;Is the data portable?&quot;</description>
		<content:encoded><![CDATA[<p>I s&#8217;pose you could ask the same of any other related product. Fer instance, this press release headline of yesterday:</p>
<p>&#8220;COADE releases CADWorx P&amp;ID Professional 2010 for process and instrumentation diagrams with support for AutoCAD 2010 plus other enhancements&#8221;</p>
<p>All your questions can be boiled down to one: &#8220;Is the data portable?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wm.J.Townsend</title>
		<link>http://www.blog.cadnauseam.com/2009/09/30/trusting-autodesk-contemplating-a-new-product/#comment-3992</link>
		<dc:creator>Wm.J.Townsend</dc:creator>
		<pubDate>Wed, 30 Sep 2009 07:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.cadnauseam.com/?p=698#comment-3992</guid>
		<description>Two snivels in one evening. A landmark...

Mechanical Desktop and I had an illicit affair ever since it was an underage Designer/AutoSurf way back in 1992. It was put to sleep with the (see recent 2010 whine) 2009 release. We had sixteen out of seventeen happy years together. Sharing those MDT files with others was never easy. Won&#039;t be a problem in the future.

Autodesk wants me to embrace Inventor. I&#039;ve had Inventor since June of 1999. Ten years. It has never worked for me during that decade. Won&#039;t allow me to work the way I want. Takes four to five times longer than vanilla ACAD to make some of the odd-ball thingies I make. Results are okay if I don&#039;t mind the huge time hit. And just like MDT, there&#039;s no promise that it&#039;ll be there next year. I have low expectations... But there is an upside! Just like Microstation and Solidworks - nobody has ever requested any of my projects be done with Inventor.

Then there&#039;s Mechanical. Lots of features that should make my output better. But, same file differences and proxies that MDT choked on. Other companies need object enablers for many different ACAD versions and a handful of other CAD packages. They can all read some level of standard DWG files and most can work with DXF if need be. Too much bother for simple 2d enhancements that a fistful of LSP and blocks can cover without the file drama.

So, the plug has been pulled on MDT. I have no faith in Inventor, and there&#039;s no guarantee that Mechanical will be an ongoing vertical. I do feel comfortable using straight (&#039;tho heavily customized) vanilla AutoCAD. Almost everybody can read the files in one manner or another.</description>
		<content:encoded><![CDATA[<p>Two snivels in one evening. A landmark&#8230;</p>
<p>Mechanical Desktop and I had an illicit affair ever since it was an underage Designer/AutoSurf way back in 1992. It was put to sleep with the (see recent 2010 whine) 2009 release. We had sixteen out of seventeen happy years together. Sharing those MDT files with others was never easy. Won&#8217;t be a problem in the future.</p>
<p>Autodesk wants me to embrace Inventor. I&#8217;ve had Inventor since June of 1999. Ten years. It has never worked for me during that decade. Won&#8217;t allow me to work the way I want. Takes four to five times longer than vanilla ACAD to make some of the odd-ball thingies I make. Results are okay if I don&#8217;t mind the huge time hit. And just like MDT, there&#8217;s no promise that it&#8217;ll be there next year. I have low expectations&#8230; But there is an upside! Just like Microstation and Solidworks &#8211; nobody has ever requested any of my projects be done with Inventor.</p>
<p>Then there&#8217;s Mechanical. Lots of features that should make my output better. But, same file differences and proxies that MDT choked on. Other companies need object enablers for many different ACAD versions and a handful of other CAD packages. They can all read some level of standard DWG files and most can work with DXF if need be. Too much bother for simple 2d enhancements that a fistful of LSP and blocks can cover without the file drama.</p>
<p>So, the plug has been pulled on MDT. I have no faith in Inventor, and there&#8217;s no guarantee that Mechanical will be an ongoing vertical. I do feel comfortable using straight (&#8217;tho heavily customized) vanilla AutoCAD. Almost everybody can read the files in one manner or another.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
