Honestly, the tech stack is the last thing I consider about a job--within reason. I wouldn't consider a job where the decision was to, say, move towards Flash, or something. But even that would be as much about the other things I care about as Flash specifically.
The most important parts of a job are the team you're working with and direct management you have and the kinds of problems you get to solve.
If those things are all good, the specific stack doesn't matter. You'll grow and develop as a technologist, and hopefully in a sustainable way. As long as the choice is defensible, I wouldn't care about it at all. If it's completely idiotic (like Flash would be today), then that says a lot about the quality of management and team you'll be working with.
On the face of it, it may not be a big deal. But one thing to be wary of is a bait and switch. If you were specifically hired to do something that was a big part of your decision to take the job, and then all of that goes away, that's a bit of a flag, regardless of how acceptable a legacy decision might be on its own.
I would try and figure out that piece of the puzzle: did the hiring manager manipulate you to get you to take the job? OR was this a decision that was still largely in progress and you're coming to grips with some slightly wishful thinking?
One of those is a legitimate problem. The other is possibly some excitement and enthusiasm that was a little misplaced.
The most important parts of a job are the team you're working with and direct management you have and the kinds of problems you get to solve.
If those things are all good, the specific stack doesn't matter. You'll grow and develop as a technologist, and hopefully in a sustainable way. As long as the choice is defensible, I wouldn't care about it at all. If it's completely idiotic (like Flash would be today), then that says a lot about the quality of management and team you'll be working with.
On the face of it, it may not be a big deal. But one thing to be wary of is a bait and switch. If you were specifically hired to do something that was a big part of your decision to take the job, and then all of that goes away, that's a bit of a flag, regardless of how acceptable a legacy decision might be on its own.
I would try and figure out that piece of the puzzle: did the hiring manager manipulate you to get you to take the job? OR was this a decision that was still largely in progress and you're coming to grips with some slightly wishful thinking?
One of those is a legitimate problem. The other is possibly some excitement and enthusiasm that was a little misplaced.