>Another thought would be to embrace and use the terms that are popular >today. Names change, even when the ideas remain the same. You can't >fight that. This is nothing unique to software engineering, it's just >human nature. I can't tell you how many times my parents have said to >me, "In my day, we used to call that...."
I think the reason names change is well the basic concept may fit the bucket of something else, they're not specific enough to the actual problem. Personally, I found the term "Unobtrusive JavaScript" extremely intuitive and specific. On the other hand the phrase "Applying Software Engineering Principles to Web 2.0 Development" is very general and vague (as it could directed to lots of aspects of your development process.) Not criticizing, just trying to point out why I think often new terms crop up to describe old patterns.
