Never having used a Mac, I'm blissfully ignorant of all the goodness I'm reportedly missing out on, although my wife brought one home the other day. She's struggled with PCs from day one, and I'm probably not helping because she calls on me for advice and I have to plead guilty to making my frustration (with her inability to be as intuitive as Bill Gates) obvious. I'll be interested to see if she copes with it better, because like Sgt. Schultz, I know nothing. I'm not in any of the higher echelon categories for CAD needs, being an occasional designer, occasional fabricator, occasional draftsperson, but I do know what to do with it. I've used TurboCAD as a generic CAD doall for probably ten years, and still do. Back to back, I prefer TurboCAD's interface to ViaCAD's. I draw and model from 2D primitives more than features, but even features are easier for me to find and orient from in TC. That's probably inexperience with VC, I've still got a long way to go, but I'm giving serious thought to Shark LT. The reasons why I use like to use VC: it appears to be more stable than TurboCAD for some tasks. It appears to leverage some of the ACIS features better than TC, ie blending and shelling, and if it can't do it, VC gives a coherent meaningful reason that often gives a clue as to how to go about getting it done via workaround. TC is obtuse if it can't do something, so I often transfer a .sat object to VC, blend or shell, then put it back into TC. ViaCAD is much better at combining solid and surface elements, replacing surfaces or producing parametric surfaces (that spline import feature rocks), and it's got some surface shape production methods that TurboCAD doesn't ie net, skin and cover surfaces. Birail works better, too. That being said, VC is as obtuse as TC with some messages like "curves not connected!".
Some of the nicer features of Shark attract me. Booleans on surfaces, not just solids. Advanced capping and lofting with guides. Until I've worked up inarguable (with my wife) justification for Shark, the Rhino import for TC costs $50, so VC is a good deal purely as a Rhino importer. Aside from that, TC and VC transfer seamlessly with .sat for solids, dxf, IGES or STEP for 2D.
I first heard about CU around version 2, so sampled it back then. I'm still not in the market at the CU/SharkFX price point, so I'm lucky that VC became available. FX now has the same sorts of constraints that've been in TC Pro for a while, so that's something that I've some familiarity with. I don't use them very often, and I have even less requirement for pure parametrics. When I do need parametrics, well, then there's Alibre, which is free for the "lite" version, but which can only save 10 entities in one file. That's about the most I need. Again, .sat is the transfer medium of choice.
So, with the OS that a lot of you don't like, I'm spoiled for choice. So Windows isn't elegant? Neither am I.
murray