Tag: <span>BricsCAD V17.2</span>

Bloatware – a tale of two installations

In a previous post, I showed that AutoCAD is bloatware by comparing the size of its downloads to that of BricsCAD. Obviously, an application that’s ten times the size it should be is going to cost you a lot of unnecessary bandwidth, download time and drive space. But maybe you don’t care about that. What practical difference does it make? Well, for one thing, the blimping-out of Autodesk’s former flagship product has a big effect on installation time. Vast and ever-increasing amounts of time are wasted by users of Autodesk products, just waiting for the things to finish installing. But …

Bloatware – a tale of two CAD applications

You may have seen me mention in passing that AutoCAD is bloatware. That’s not just the general grumpy-old-user moan you see from long-term users like me, who can remember when AutoCAD used to fit on one floppy disk. Yes, programs get bigger over time as new functionality is added and old functionality needs to be retained. Hardware gets bigger, better, faster over time to compensate for that. I get that. Understood. The AutoCAD bloatware problem is much more than that. AutoCAD is literally ten times the size it needs to be, to provide the functionality it does. How do I know? …

Bricsys shows Autodesk how to do mid-term updates

BricsCAD V17.2 is out. Although there’s nowhere near as much new and useful in this mid-term update as in the full upgrade from V16 to V17, there’s more here than in Autodesk’s last mid-term update, AutoCAD 17.1. There’s even arguably more than in the uninspired AutoCAD 2018 upgrade, including those 17.1 features. But that’s not the main reason I say Bricsys is schooling Autodesk in how to do mid-term updates. While Autodesk is restricting such updates (including the bug fixes and security updates included in those updates) to subscription and maintenance customers, Bricsys is doing no such thing. BricsCAD V17 …