Developer's Toolkit

Blog archive

Not a Day at the Beach

As the heat index in New England once again gallops past a hundred degrees, I am safely ensconced in my basement, where the primary source of heat is my own agitation at yet another round of software upgrades. In this case, it was the Adobe Acrobat Reader, but it could just have easily been any of the several dozen applications I have on my system.

When I launched the Acrobat Reader, I got the notification that there was a new version available, and thought, What the heck, I have a few extra minutes this morning. Well, three reboots, one hung system, and one hour later, I finally had the latest version of the Acrobat Reader on my system. And somewhere in the interim, I rather forgot what I was going to do with it.

The disingenuous thing was that Adobe called two of the updates critical security releases. Sound familiar? (If not, I still have the Windows Genuine Advantage sitting in my Updates cache as a critical update). How could you not install that?

Now, I am not intentionally singling out Adobe; other software vendors engage in similar practices. And Adobe may well respond that the hour I spent upgrading is a trivial amount of time, especially when balanced against a more secure system. And within that company's microcosm, it is correct.

But multiply this experience by the thirty-seven applications I have on my system (I counted), and it has the potential to become a full-time occupation, or at least a significant drag on productivity. Yet it makes perfect sense from the standpoint of individual software companies, because taken individually, the effort is minor.

In 1968, Garrett Hardin published an essay in Science called "The Tragedy of the Commons" (http://en.wikipedia.org/wiki/Tragedy_of_the_commons), in which he postulated the then-radical notion that when resources were finite, each person pursuing their own self-interest in maximizing their individual return would in fact not even come close to maximizing the use of that resource for all. Applied to my situation, it stands to reason that software companies are engendering no good will by working to their own individual advantage.

My system is a Windows system, and my applications Windows (or Web) applications. I have limited recent experience with Linux and open source software. I wonder if the open source model is better at addressing the issue of finite end user resources. Any thoughts?

Posted by Peter Varhol on 08/02/2006


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube