Advertisement
Search  
Always will be ready notify the world about expectations as easy as possible: job change page
Oct 20, 2023

Continuous Obsolescence

Source:
Views:
1798

AntiPattern Problem

Technology is changing so rapidly that developers have trouble keeping up with the current versions of software and finding combinations of product releases that work together.

Given that every commercial product line evolves through new product releases, the situation has become increasingly difficult for developers to cope with. Finding compatible releases of products that successfully interoperate is even harder.

Continuous Obsolescence

Java is a well-known example of this phenomenom, with new versions coming out every few months. For example, by the time a book on Java 1.X goes to press, a new Java Development Kit obsoletes the information. Java is not alone; many other technologies also participate in Continuous Obsolescence.

The most flagrant examples are products that embed the year in their brand names, such as Product98. In this way, these products flaunt the progression of their obsolescence. Another example is the progression of Microsoft dynamic technologies:

  • DDE
  • OLE 1.0
  • OLE 2.0
  • COM
  • ActiveX
  • DCOM
  • COM?

From the technology marketers' perspective, there are two key factors: mindshare and marketshare. Rapid innovation requires the dedicated attention of consumers to stay current with the latest product features, announcements, and terminology.

For those following the technology, rapid innovation contributes to mindshare; in other words, there is always new news about technology X. Once a dominant marketshare is obtained, the suppliers' primary income is through obsolescence and replacement of earlier product releases. The more quickly technologies obsolesce (or are perceived as obsolete), the higher the income.

Refactored Solution

An important stabilizing factor in the technology market is open systems standards. A consortium standard is the product of an industry concensus that requires time and investment.

Joint marketing initiatives build user awareness and acceptance as the technologies move into the mainstream. There is an inherent inertia in this process that benefits consumers, for once a vendor product is conformant to a standard, the manufacturer is unlikely to change the conformant features of the product.

The advantages of a rapidly obsolescing technology are transitive. Architects and developers should depend upon interfaces that are stable or that they control. Open systems standards give a measure of stability to an otherwise chaotic technology market.

Variations

The Wolf Ticket Mini-AntiPattern describes various approaches that consumers can use to influence product direction toward improved product quality.

Similar
May 29, 2023
Maximizing performance in asynchronous programmingTask and Task<TResult>The Task and Task<TResult> types were introduced in .NET 4.0 as part of the Task Parallel Library (TPL) in 2010, which provided a new model for writing multithreaded and asynchronous code.For demonstration purposes, let’s...
Oct 24, 2023
Author: Pen Magnet
Passion is both the reason and the rewardI entered the software industry about 2 decades ago. I was an engineering graduate, but I didn’t have a computer degree.It was OK, not only because I knew the basics of software making...
Oct 21, 2023
AntiPattern ProblemObject-oriented analysis and design (OOA&D) models are often presented without clarifying the viewpoint represented by the model. By default, OOA&D models denote an implementation viewpoint that is potentially the least useful. Mixed viewpoints don't allow the fundamental separation of...
Oct 21, 2023
BackgroundFunctional Decomposition is good in a procedural programming environment. It's even useful for understanding the modular nature of a larger-scale application.Unfortunately, it doesn't translate directly into a class hierarchy, and this is where the problem begins. In defining this AntiPattern,...
Send message
Email
Your name
*Message


© 1999–2024 WebDynamics
1980–... Sergey Drozdov
Area of interests: .NET Framework | .NET Core | C# | ASP.NET | Windows Forms | WPF | HTML5 | CSS3 | jQuery | AJAX | Angular | React | MS SQL Server | Transact-SQL | ADO.NET | Entity Framework | IIS | OOP | OOA | OOD | WCF | WPF | MSMQ | MVC | MVP | MVVM | Design Patterns | Enterprise Architecture | Scrum | Kanban