>It is interesting to note that the 'COM/Win DNA Model' lasted about five years. It started around Office 97/VB5/VBA integration. It was an amazing innovation/development by MS. And only five years later it became 'legacy'. It does make you wonder how long MS will stick with its current paradigm. I wonder if we've reached a stage in software development where more developers are making software in 'outdated/legacy' languages versus evolving/modern languages.

I really dont know Dave. I guess I would ask who decides whats considered "outdated / legacy". Does something new automatically make everything else old? What if the old stuff is also being upgraded? Is it still old? Or old/new? I think this idea is perhaps an interesting topic of discussion but not of great practical value.

I do believe that end-users, corporate and individuals, are getting tired of the endless upgrade cycle. Not everybody needs or wants the latest greatest that Win-Tel can produce. Sometimes "good enough" is good enough.

I have been around long enough to see langauges (and other tools/platforms) come and go with all the hype and buzzwords and absolute assurances from the vendors that "this was the next big thing". Its complicated to forecast the IT (any) world. .Net's future dominance is not guaranteed. The open source movement is huge and other languages like Java and Delphi are not bit players but forces to be reckoned with. I think the future is uncertain.

If you have tools that help you perform your job well and you can make money from them, then good. Keeping an eye on things and learning new stuff is part of the job - no problem.