Tag Archives: BricsCAD V17.2

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 isn’t this just the inevitable price to pay for the functionality provided?

No. Again, BricsCAD proves it.

The installation comparison is shown below. These installations were performed on a mid-range Windows 10 i7 PC with 8 GB RAM. The downloaded files were executed from a local hard drive and the applications were installed to a local SSD. If I needed to enter information manually, I stopped the clock while that was going on. Times are the total elapsed time from commencement in minutes and seconds. More user input was required for the AutoCAD install, but that has not been counted in this comparison. That is, by eliminating the human input stages I’m being kind to Autodesk.

I performed a complete default installation of BricsCAD. In the case of AutoCAD, I turned off the installation of Recap and A360 Desktop to make for a fair comparison, as equivalents are not part of the BricsCAD install and those components are not required by the average CAD user. Everything else was as per default settings.

BricsCAD V17.2 64-bit Windows Installation
Installation Operation
Timestamp
Execute BricsCAD-V17.2.03-1-en_US(x64).msi 0:00
Prompt for questions 0:03
Click Yes for UAC Allow 0:14
Installation complete, start application 0:35
First run startup 0:40
Total time from install to ready to draw
0:40 (100%)

That’s astonishingly fast. Remember, this is an application that is more capable than AutoCAD overall. How does installing AutoCAD itself compare?

Equivalent AutoCAD 2018 64-bit Windows Installation
Installation Operation
Timestamp
Execute AutoCAD_2018_English_Win_64bit_dlm_001_002.sfx.exe 0:00
Self-extractor finishes initializing 2:46
Self-extractor finishes extracting, click Yes for UAC Allow 4:56
Install screen appears, answer questions, start install proper 5:04
Desktop icon appears 8:10
Install complete, restart required 10:21
Restart complete, start application 11:41
Activation begins 12:05
Activation complete 12:21
Close AutoCAD, execute AutoCAD_2018_Product_Help_English_Win_32_64bit_dlm.sfx.exe 12:25
Self-extractor finishes initializing 14:44
Self-extractor finishes extracting, click Yes for UAC Allow 14:54
Install screen appears, answer questions, start install proper 14:57
Offline Help installation complete, execute AutoCAD_2018.0.1_64bit_r2.exe 15:44
2018.0.1 install complete, start AutoCAD 16:50
Second startup complete 17:18
Total time from install to ready to draw
17:18 (2595%)

Installed sizes are roughly 0.5 GB for BricsCAD and 2.4 GB for AutoCAD. It’s hard to be exact because Autodesk likes to perform multiple installs when one is requested and tends to squirrel away various components in a variety of places. Here are the ten(!) new entries in Add or Remove Programs after just the first stage of the AutoCAD install:

OK, so maybe AutoCAD takes 26 times as long as BricsCAD to install. But the AutoCAD installation images are so much prettier than the plain old BricsCAD dialogs! Shall we call it a draw?

No.

Autodesk, you took a real pounding here. Bricsys chewed you up, spat you out, ground the chewings into the dust, set fire to the remains and then put out the fire with bodily fluids. Sorry, but you deserve it. Your installations have been ridiculously slow for years and are getting worse. Installing a vertical product or suite is beyond a joke; it makes even the AutoCAD install look speedy. It’s not good enough.

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? BricsCAD proves it. Here’s what I mean.

BricsCAD V17.2 64-bit Windows Download
Downloaded File Size (KB)
BricsCAD-V17.2.03-1-en_US(x64).msi 248,812
Total (1 file) 248,812 (100%)
Equivalent AutoCAD 2018 Downloads
Downloaded File Size (KB)
AutoCAD_2018_English_Win_64bit_dlm_001_002.sfx.exe 2,065,829
AutoCAD_2018_English_Win_64bit_dlm_002_002.sfx.exe 328,277
AutoCAD_2018.0.1_64bit_r2.exe 120,663
AutoCAD_2018_Product_Help_English_Win_32_64bit_dlm.sfx.exe 180,013
Total (4 files) 2,694,782 (1083%)

Which dog is which? They’re both cute, but which would you put your money on in a race?

(Original image: Przykuta)

(Original image: Lisa Cyr)

I’m actually being very generous to Autodesk in this comparison. The two primary AutoCAD download executables alone expand from 2.4 GB to 5.2 GB before install, requiring a total at least 7.6 GB of disk space before we even get to the same ready-to-install point as BricsCAD’s 0.24 GB MSI file.

No, it’s not because BricsCAD is a cut-down application compared with AutoCAD. The opposite is true. Overall, BricsCAD is significantly more feature-rich than AutoCAD. It near-exactly duplicates over 95% of AutoCAD’s functionality and then adds a big slab of its own on top of that. Some of it is in paid-for optional extras, but the code that provides that functionality is still included in the same small download.

This issue isn’t unique to AutoCAD. Super-morbid obesity seems to be standard among Autodesk products. The AutoCAD-based verticals that add a comparable level of functionality to that the BricsCAD download includes are much bigger again!

Anybody care to explain what’s going on here?

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 customers who have a perpetual license, even without maintenance (called All-In by Bricsys), will be receiving V17.2 free of charge. Bricsys still considers such users as customers who have paid good money and still need to be looked after, rather than a non-paying irritant, which appears to be Autodesk’s attitude.

Oh, and you don’t have to install some piece-of-junk automatic updater or malware-like download manager to get the software. You just do a straightforward browser download of a small file (by Autodesk bloatware standards) which is the entire product, and install over the top of your existing installation, effortlessly preserving your settings. If you’re doing a new install of V17.2 from scratch, you just install from that downloaded product. No need for multiple downloads and multiple-step installations. No need to have every PC in your fleet nagging your users and downloading the same huge files.

Autodesk isn’t in the hunt here for ease of maintenance. Not remotely in the same league. Seriously, go home and start again, Autodesk. Your ideas are bad and your execution is worse.

Here are some links to information about the V17.2 update (not neutral sources, obviously):

I will be benchmarking BricsCAD V17.2 and AutoCAD 2018 with great interest. In my preliminary tests, BricsCAD V17.0 performance walked all over AutoCAD 2018 in most areas, but commands involving object selection were the exception, with AutoCAD significantly quicker there. Bricsys is claiming large improvements in that area, but we’ll see.