The big Bricsys interview 10 – platforms

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh. In this post, R.K. McSwain asks about BricsCAD running on three different platforms. Erik explains why BricsCAD for Mac (and Linux) is so much more complete than AutoCAD for Mac, which has more holes than a block of Swiss cheese. R.K.: Do all three platforms (Windows, Linux, Mac) contain the same functionality? Erik: Yes. Sometimes it’s a bit hard with the Mac to bring it along but so far, so good. The only problem sometimes is …

Executive summary of Deelip’s AutoCAD for Mac interview

Deelip has just published an extensive interview with several Autodesk people about AutoCAD for the Mac. Deelip had a good set of questions and I suggest you read the whole thing, but if it’s all too tl;dr for you, then here is the lazy reader’s version of what Autodesk had to say: The AutoCAD code was split up into 3 sections: the core CAD engine (platform-independent), the Windows-specific (MFC) parts and the Mac-specific (Cocoa) ones. AutoCAD for Mac is incomplete. Choosing which features to leave out was done with the aid of CIP (oh, dear) and Beta feedback. (Hang on …

AutoCAD for Linux – another bad idea

I often see calls for Autodesk to support AutoCAD on Linux. Just like AutoCAD for the Mac, while I can sympathise with the users of that OS, I think a native port of AutoCAD for Linux would be a bad idea. Again, I think it would be bad for everybody: Autodesk, AutoCAD for Windows users, and most of all, AutoCAD for Linux users. Why? First of all, for most of the same reasons I gave for the Mac port. Autodesk hasn’t just failed in the past with AutoCAD for the Mac, it has failed with AutoCAD for Unix, too. I …