These are interesting times.
Microsoft's operating systems are seen by many as bloated and porus which leaves many opportunities for breaches. It is also an ideal target.
If it were not for Symantec and McAfee and similar efforts, Linux and other alternatives would be far more popular with the less technically ("normal users") inclined.
Microsoft's efforts to close the holes is reasonable but limited. Marketed to the "masses", the "masses" have neither the experiencce or bandwidth to keep their machine "current" or to restore functionality. Microsofts effort is late, but welcome.
For all-to-many, the Windows updates are simply too-little-too-late. A botched update is simply catastrophic for most "users". An infected machine is slow or unstable for most users. There is a widespread frustration world-wide because their systems do not work "right".
The "Web" is still a collection of evolving innovations and standards. In the efforts to achieve functionality and market, there will continue to be the opportunities for worms and viruses.
Does "IM" really mean "Instant Mayhem?" With ActiveX, DLL's, and easily hacked address books, quite possibly. With functional constraints, XML messaging, and a "standard" API that is not compromised by individual parties, it can "IM" be stable and safe. (keep "IM" in a sandbox)
Actually, right now is the ideal time to introduce low cost the Internet-ready workstations that were suggested a few years ago. If developed on a tight OS with secure applications, it would give the masses a real break from "fear, uncertainty, and doubt marketing", worms, and viruses.
Can we look to Embedded Linux, XML, and Java? Perhaps if the Linux system provider had better control over the hardware and made it simplier for the "local expert" to update, with external access for adding memory, we'd have fewer "customization" kills and compatibility problems. The drawback to Linux, of course, is a dead Linux system is very dead for "normal" computer users. (most "local experts" are best kept local)
An updatable "get-out-of-jail" PCMCIA "WebStation" program card, would make recovery much easier for most users. Knowing they have some resilience, users will be more comfortable with alternatives.
"Recovery Sequence of Operations"
1) Power on Machine (booting does not matter)
2) Insert Card which exposes a "Doit" button
3) Press the "Doit" button
4) Watch the Dancing Duke, Penguin, or whatever logo we put in the firmware.
Contrary to Microsoft propoganda, Java is secure by design. Most users do not know what Java is (except what Microsoft tells them), but will respond to slow load times. If loading classes by name is adopted for "extensions", then Java is vulnerable to attacks as well. (addressible)
Most users do not know what XML is (except what Microsoft tells them), but will respond to slow I/O times and bloated memory requirements. However, adopting XML for data will address the countless remaining buffer overrun breach opportunities in Windows and its programs.
The protection we have from the mayhem the current hackers provide mostly comes from the third party virus protection package we buy. These packages can not make the underlying operating system any better suited for widespread use. Nor, can these packages fix all infections or deficiencies.
This is where we are.
"Gentlemen, we are looking at a great opportunity."