> and that code cannot do a lot of bad stuff, True now. But Microsoft made a contribution in this area too. Active-X plugin's were effectively DLL's you down

> and that code cannot do a lot of bad stuff, True now. But Microsoft made a contribution in this area too. Active-X plugin's were effectively DLL's you downloaded and then IE attached to itself. Since they ran as IE they could do anything IE was allowed to do - like modify most files on disk, including the OS. The customer got a plugin that could do literally anything the browser was allowed to do to the disk, display, network and OS, and it being native code Active-X plugins were quuuuuick. Microsoft got lock in. Security disaster understates it of course. They were rightfully treated like toxic waste by very browser except IE. My real point is Microsoft has form in this area. And it's form that continues to this day. They could have made VBA as safe as Javascript over time by perhaps introducing a safe version that was always allowed to run, and made the dangerous variant harder and harder to unlock. They've never showed the slightest interest in doing so. Instead they ship "Windows Defender", which is about as effective as a week old cotton mask in a COVID ward. Come to that they could have provided a Windows environment as safe as iOS and Android, and migrated everything in over the course of a decade or two. Again - not the slightest hint. Instead they apparently prefer to keep their systems insecure, and sell yearly licences to half arsed fixes like Intune to businesses who can afford it.