feature article
Subscribe Now

Why Do We Install Software?

Exploring the Technical Reasons Behind an Old Procedure

“I can install toilets. I’m learning how to do basic wiring.” – Sandra Bullock

Why do we “install” software on our PCs, phones, and sometimes even embedded systems? Why don’t new programs just run right out of the box without going through the whole installation process? 

The procedure for installing (and later uninstalling) seems to go through phases over the years. With big room-sized machines attended by lab-coated technicians, you literally did install new software, in the sense of plugging in different boards, wires, and circuitry. Even though those early computers were programmable, the programs themselves were hard-wired. 

Videogame consoles didn’t always make you install games. You just plugged in the newest Nintendo cartridge and it ran. Uninstalling meant yanking the cartridge out. Same deal for early PCs with programs on cassette tape or floppy disk. 

Embedded systems mostly avoid the installation processes, but that’s by default, not by design. One good definition of “embedded system” is “any machine that ships with all the software it’s ever going to have.” No aftermarket software? No need to install it. The operating system and its applications are one and the same, now and forever, amen. 

But Windows, MacOS, Linux, and other modern operating systems make us go through an install process for each new program. What’s up with that? Same goes for smartphones, although the installation is largely hidden as part of the vendor-mediated download. 

We take it for granted, but why is installation even necessary? Why can’t we simply load and run new programs like those old video game cartridges? Skipping the installation step would improve the “out of box experience” for new applications. It would also eliminate the painful and often unsuccessful uninstall process, which invariably leaves unwanted cruft behind. Most of all, skipping the install/uninstall procedure would leave the operating system untouched and comparatively reliable. There’s also no downside to checking out one of the few remaining sites to get freeware

Granted, there are some cases where an install process seems warranted, as when the program insinuates itself into the operating system’s GUI. Sometimes we want to right-click a Windows file and have the new app’s options appear in the pop-up context menu alongside the standard OS options. That’s slick, and it clearly needs integration with the Windows GUI or it wouldn’t work. 

Cloud storage options (OneDrive, iCloud, Dropbox, et al.) fall into this category, too. They need deep OS integration in order to appear seamless, and that requires an install process and a reboot. Sometimes you need to hook an interrupt, change a driver, or fiddle with file associations. Okay, I get that. 

But what about the other 95% of apps we install? Why do spreadsheets, word processors, email programs, games, web browsers, weather monitors, and other familiar miscellany need to spend the first 20 minutes of their lives going through an extensive install process? Why does anything from Adobe take so long? What deep OS integration do they need that wouldn’t be better accomplished by just… running? 

I’m convinced that eliminating software installation completely would make operating systems faster and more reliable. That goes for desktops, laptops, phones, embedded systems – all of it. Without third-party tinkering, the OS and its drivers would remain just as the developer intended. API calls can (or should) provide all the interface that third-party apps need. All application-related files stay in their own directory/folder, and “uninstalling” consists of deleting that directory tree. No muss, no fuss, no leftover detritus. Is your system slowing down over time as you install more programs? Can’t blame the installer. 

Debugging gets a lot easier, too, because you’re not left wondering how much of the code is really the OS vendor’s work and how much has been tampered with by a succession of installed/uninstalled applications and drivers over time. Better yet, digitally sign each executable file so you always know exactly whose code you’re looking at. 

Or, we could just rethink this whole reprogrammable computer thing and treat everything as a closed embedded system with all the code in OTPROM. The factory gets one shot at shipping code before it’s set forever. Better yet, replace all the software with hard-wired circuits. Then replace the circuits with real hardware, circa 1890. That’ll fix them ornery bugs.

Leave a Reply

featured blogs
Dec 8, 2023
Read the technical brief to learn about Mixed-Order Mesh Curving using Cadence Fidelity Pointwise. When performing numerical simulations on complex systems, discretization schemes are necessary for the governing equations and geometry. In computational fluid dynamics (CFD) si...
Dec 7, 2023
Explore the different memory technologies at the heart of AI SoC memory architecture and learn about the advantages of SRAM, ReRAM, MRAM, and beyond.The post The Importance of Memory Architecture for AI SoCs appeared first on Chip Design....
Nov 6, 2023
Suffice it to say that everyone and everything in these images was shot in-camera underwater, and that the results truly are haunting....

featured video

Dramatically Improve PPA and Productivity with Generative AI

Sponsored by Cadence Design Systems

Discover how you can quickly optimize flows for many blocks concurrently and use that knowledge for your next design. The Cadence Cerebrus Intelligent Chip Explorer is a revolutionary, AI-driven, automated approach to chip design flow optimization. Block engineers specify the design goals, and generative AI features within Cadence Cerebrus Explorer will intelligently optimize the design to meet the power, performance, and area (PPA) goals in a completely automated way.

Click here for more information

featured paper

Universal Verification Methodology Coverage for Bluespec RISC-V Cores

Sponsored by Synopsys

This whitepaper explains the basics of UVM functional coverage for RISC-V cores using the Google RISCV-DV open-source project, Synopsys verification solutions, and a RISC-V processor core from Bluespec.

Click to read more

featured chalk talk

dsPIC33CH DSCs: Two dsPIC33Cs on a Single Chip
Sponsored by Mouser Electronics and Microchip
In this episode of Chalk Talk, Vijay Bapu from Microchip and Amelia Dalton explore the benefits of dual core digital signal controllers. They discuss the key specifications to keep in mind when it comes to single core and dual core DSCs and how you can reduce your development time, save board space and cost and keep the performance and isolation you need with Microchip’s dsPIC33CH DSCs.
Jan 24, 2023
37,634 views