Is HTML the new legacy?

What can we do about legacy?

Legacy modernization has a very high cost tag. In many situations the price of modernization is completely discouraging.

As a thread of discussion on Twitter, @tk300 suggests a disciplined attitude to limit the problem:

But this applies only to new legacy, not the one that has already been produced in RPG,COBOL, ADA, PL/1, HTML or even Java?

And even if we decide to follow this advice, this probably means that we should also stop innovation?

May be we could think of new techniques that will produce software easy to evolve or to recycle?

This entry was posted in ADA, COBOL, HTML, Legacy Modernization, PL/1. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s