If a failed update or crash has ever ruined your afternoon, you're not alone: Andrew S. Tanenbaum claims that Windows has so many bugs because its technical framework is so vast that not even its own manufacturer controls it completely.
Key figure in academic computing, Author of “Operating Systems: Design and Implementation” and creator of MINIXTanenbaum brings context and insight to the debate about the stability of the systems we use every day and the way they are built.
A system so big that no one fully controls it
According to the academic, the size and tangle of Windows dependencies make it any change can trigger side effects difficult to anticipate. Hence the succession of patches arriving each week and the risk that, when one bug is fixed, new ones will appear.
For him, Many critical systems (including Windows) have been built as large monolithic blocks where everything is interconnected. This lack of isolation between components complicates maintenance and increases the likelihood of instability and security holes.
Tanenbaum goes so far as to say that in organizations of that size No engineer understands even a significant fraction of the total codeWhen you touch one piece of the puzzle, it's almost impossible to predict what else will break. His reflections come from an extensive conversation with the Argentine newspaper Clarín.
Monolithic vs. Modular: Lessons from MINIX, Linux, and Windows
The professor contrasts that approach with the modularity of MINIX and alternatives such as Anduinos: If the audio driver fails, the damage is limited to the sound. You shouldn't have permission to touch the puck or the net, so the real impact is limited and recovery is easier.
In monolithic systems, such as Windows or Linux itself, for example LinuxFX, the pieces are much more intertwinedA flaw in one module can propagate and trigger cascading problems: crashes, persistent errors, and gaps that require further fixes.
This debate is not new. Tanenbaum, a proponent of a microkernel and modular approach, He exchanged arguments with Linus Torvalds, a supporter of a monolithic kernelThe dispute encapsulates a classic dilemma: performance and simplicity of implementation versus isolation and security.
Market reality has favored monolithic designs, but Tanenbaum questions whether this “victory” makes up for it. when costs are measured in stability, attack surface, and long-term maintenance. His thesis: a somewhat slower but compartmentalized system can be much more resilient.
Closed software and opacity: what we don't see
Beyond Windows, the computer scientist warns that much of the commercial software It operates as a black box, opaque even to its own teams.; however, initiatives such as Microsoft open sources part of WSL code show that transparency can improve internal auditing and understanding.
For users and organizations, this means living to the rhythm of patches and blindly trust updates, while dependencies and side effects multiply. More modular engineering, permitting, and independent audits would help reduce risks without slowing innovation.
Tanenbaum's perspective draws an uncomfortable diagnosis: Uncompartmentalized complexity makes Windows a breeding ground for errors, keeps teams busy with continuous fixes and increases exposure to security flaws; rethinking the architecture toward well-isolated modules appears to be the most solid path to achieving stability.
