The more time I immerse myself in SW, the more warts I find. It was pretty keen when you rely on the demo & some lessons, but it has flaws too.dgs said:It's funny to me how folks will say SW or Pro|E suck because of this or that and then tell me how the other is clearly superior. Then they go on about how the bad one is loosing customers, etc. No facts or data, however. I can't say if one or the other is gaining or loosing, don't know if there is such a study. I know that PTC claims that Pro|E is not slipping, but actually growing faster than the overall MCAD market (15% vs. 5%, as stated at PTC|User in Tampa).
In my recent experience with SW 2006 (I'm now working with 2007 and appreciate that you can now save a model in insert mode.), I was surprised to find just as many stupid little annoyances as in Pro|E. Like setting a part transparent makes selecting hidden edges real hard. Like the measure tool sometimes deactivating itself after clicking the first reference. Like not being able to dimension to surfaces and edges failing when you redefining a feature. Like not being able to find where a sketch is in the model tree. Like having a hard time distinguishing between mates that constrain that component and mates that constrain something else to that component. Like not knowing where the sketches are in the tree.
If I had been on SW for years I'd dismiss these things as just being the way it is. But Pro|E isn't that way. Of course, Pro|E won't let you move on and fix it later when something fails like SW (which is great).
They're both good tools, I like Pro|E better. To me, SW feels less robust. Can't put my finger on it, it just feels less capable and like I'm getting close to the limits f its capabilities and I'm always working around it's limitations. A good portion of that is probably me trying to do things the Pro|E way, the same is true of SW folks coming to Pro|E - they keep trying to do it the SW way.
There's a price too, when you slide the feature set to the top of the menu.
PTC is slow to recognize that some oft-used functions really need to be in the core package, instead of always be a user "roll-your-own."
------------------------
As for user assertions & unfounded death-knells:
Is this "voodoo thinking" on the part of users?
Want it bad enough - use it to cajole the company - and it will happen?
Wishing it hard enough, make up a scenario - makes it so?
Edited by: gamauf