Right now, I work on a small team at a large company doing Java / J2EE web applications. My original skillset wasn't in this area, but I'm starting to get the hang of things and get some more responsibilities on the team. However, our team is in a bit of limbo, and we're unsure of the future direction of our flagship application (we're J2EE, and the majority of the teams in our group working on mainframe applications.
An opportunity has been brought to my attention on another team with opportunity for career growth and working with several people I already know. The problem is that the application they support is quite legacy, running Classic ASP with little to no push to move to a newer technology or technique.
Part of me thinks that the move would possibly stagnate my skill development, working on a legacy app in a "legacy" language. I do work on my own, picking up ASP.NET MVC, Python/Django, etc., but there obviously seems to be a difference between working in those areas professionally and just doing it on my own.
Does moving into a legacy code base and legacy platform hinder my overall career? I don't want to be pidgeonholed by any move...