Our Disclaimer for PTC's Pro/Engineer Wildfire Articles




Home > Technical Articles > A New Outlook on Wildfire > Our Disclaimer

Our Disclaimer
An opinion by Eldon Goates, May 2003

As an addendum to the article A New Outlook on Wildfire, I need to emphasize that these are my opinions. I fully admit that I may be missing key items and will be happy if someone will point out where I've gone wrong. To be fair, I sent the list of issues to PTC to allow them to respond - intending to share their views with mine, but I guess their arrogance exceeds their intellect because their only response was "Get used to it".
My experience with Wildfire, though limited, also includes 3 days in Boston at PTC reviewing Wildfire in July 2002. At that time, many of the PLM's explained in detail their direction and why. It was enlightening, and you can read my comments from that meeting. I have to say I was much more impressed (with what now appears to be mostly propaganda) there, than I am now that I've actually tried to be productive with it.
For the record, I don't excuse my accusations, as I feel there is plenty of ground for such. These comments may also stem from a continued frustration with PTC over the pitiful introductory record, and may be emphasized by the disappointment I feel having bought their promises that it would be different this time. They said the right words, but couldn't deliver. The rest is just excuses.
As a note in their defense, I am impressed that I was able to work with Wildfire for a whole day without a crash. That is certainly progress. It wasn't true for the other days, but the crashes were fewer than in previous versions straight out of the box.
For PTC, I wish to remind you that we offered to assist you in trouble shooting and evaluating the software months ago. You declined. That's OK, but in your desire to not have to deal with reality (namely having us find your bugs and point out the issues) you have missed the boat. In your development you should have included some real users that aren't afraid to speak up. Now it's in production and all the bragging is but an embarrassment. I feel sad for you, and I feel even worse for all your "customers."
As indicated in the beginning, I cannot state strongly enough: DO NOT migrate to Wildfire! Furthermore, new customers should think twice about purchasing it. Pro/Engineer 2001 is now pretty stable, so that is a far better choice - even though it also has it's host of annoying issues - at least you can get the work done.

I may play a bit more with Wildfire before I delete it from my computer, but it will be a long time (if ever) before I switch over.

For additional reading:

If you're surprised by the recommendations or just want to read more of our view on Pro/Engineer Wildfire, please try the following subsections of this article:

A New Outlook on Wildfire

The Long Detailed List of Issues

Alternatives to taking the Wildfire Poison Pill

A Recommendation to PTC

Our Disclaimer

If you're interested in our first look at Wildfire, please read What About This Wildfire Thing??

Our Disclaimer An opinion by Eldon Goates, May 2003
	As an addendum to the article A New Outlook on Wildfire, I need to emphasize that these are my opinions. I fully admit that I may be missing key items and will be happy if someone will point out where I've gone wrong. To be fair, I sent the list of issues to PTC to allow them to respond - intending to share their views with mine, but I guess their arrogance exceeds their intellect because their only response was "Get used to it". My experience with Wildfire, though limited, also includes 3 days in Boston at PTC reviewing Wildfire in July 2002. At that time, many of the PLM's explained in detail their direction and why. It was enlightening, and you can read my comments from that meeting. I have to say I was much more impressed (with what now appears to be mostly propaganda) there, than I am now that I've actually tried to be productive with it. For the record, I don't excuse my accusations, as I feel there is plenty of ground for such. These comments may also stem from a continued frustration with PTC over the pitiful introductory record, and may be emphasized by the disappointment I feel having bought their promises that it would be different this time. They said the right words, but couldn't deliver. The rest is just excuses. As a note in their defense, I am impressed that I was able to work with Wildfire for a whole day without a crash. That is certainly progress. It wasn't true for the other days, but the crashes were fewer than in previous versions straight out of the box. For PTC, I wish to remind you that we offered to assist you in trouble shooting and evaluating the software months ago. You declined. That's OK, but in your desire to not have to deal with reality (namely having us find your bugs and point out the issues) you have missed the boat. In your development you should have included some real users that aren't afraid to speak up. Now it's in production and all the bragging is but an embarrassment. I feel sad for you, and I feel even worse for all your "customers." As indicated in the beginning, I cannot state strongly enough: DO NOT migrate to Wildfire! Furthermore, new customers should think twice about purchasing it. Pro/Engineer 2001 is now pretty stable, so that is a far better choice - even though it also has it's host of annoying issues - at least you can get the work done. I may play a bit more with Wildfire before I delete it from my computer, but it will be a long time (if ever) before I switch over.

For additional reading:
	If you're surprised by the recommendations or just want to read more of our view on Pro/Engineer Wildfire, please try the following subsections of this article: A New Outlook on Wildfire The Long Detailed List of Issues Alternatives to taking the Wildfire Poison Pill A Recommendation to PTC Our Disclaimer If you're interested in our first look at Wildfire, please read What About This Wildfire Thing??