Some of us have been promoting knowledge expansion for some time.

It sounds more like knowledge dilution or inferiority avoidance. They're have been projects where I have witnessed the "weakest" lobbying to use something new because it was hoped that that kind of change would even the bar. But that is a falisy. The great NOT developers of today - were/are the great java, VB and Server Page developers of yesterday. There so busy plying their trade they have little time for dev-punditing or hop-arounds! We don't have that kind of quality on this board. We do have the "hop-arounds" but they are no substitute for the depth of skill the real "heavies" would have to offer.

As you move from here to there, you achieve an thresholdof prowess and fung-sway (sp?) in your solutions. You never allow youself to excel or take the detailed challenges that might result in a sexually appealing (and satisfying) software development style. You reach a threshold. Change hats. Climb to perhaps as high a threshold as you did while wearing the last hat - change hats and do it again.

Kind of a technical lag (remember that cultural lag term referring to those locked into their youthful "best" moment of glory - the belt size changes - but it's still the same old pair of off the rack pants.)