Let's play a little game here. Assume a corporation is creating over 100 custom applications to support businesses over dozens of product divisions, and any ti

Let's play a little game here. Assume a corporation is creating over 100 custom applications to support businesses over dozens of product divisions, and any time supports over 1,000 internal applications, dating back to COBOL. The COBOL applications keep working. The ColdFusion apps keep working. The VB6 apps are supported on an XP development box, but they still work on Windows 7. People are planning the replacement applications right now. And then there's Mozilla. A feature introduced in 6 gets deprecated in 11, or changed just enough. Suddenly, 50 applications have an immediate need to change before there are any security bugs found in 10. After all, 10 is EOL and security bugs wont' be updated. The idea of a long term release (supported X years) is a good one. Enforced bit rot and continual QA on legacy apps sucks, but having to do it every few months is untenable. On the other hand, about 50 people see a market opportunity right about now. :)