@Amy – I think my point was the exact same as the one you’re making, but with an extra part.

I agree – pure AS3 devs shouldn’t work on Flex projects. But… deciding that your project is a flex project just because it’s big / long isn’t a great way to make that decision. It should be about what the requirements of the project are.

So – that’s my dispute. Though – as Jesse notes – a lot of the biggest and best projects in both technologies are for internal use only. We’ve got an awesome e-learning platform running in Air. Huge project, very custom art work, all AS3/Flash. Now self-updating, modular (in Air, with security)… very cool. No flex. 90+% test coverage. But also no public users. So – you’ll just have to trust me!

I understand the feeling of prejudice–I remember getting my panties in a wad seeing an ad for a Flash Dev who is “not dependent on the Flex Framework.” But there are a lot of things that are not the same in .fla world vs. the mxml world.

I used to feel that I was being unfairly eliminated from the running for lack of framework experience (how hard can it be?), but since I started looking into getting up to speed in the different ones, I find it’s several days solid to develop a mental map of each one that’s good enough to apply it in practice. And if an employer can find another candidate where they don’t have to bear that cost, why wouldn’t they hire them?

…then I started using it actual interviews, and got some really fascinating answers from people. It started to really give a clear picture of where people came from. Just that one question!

Some people would clearly state 1 or the other. Some would say it depends. Getting them to elaborate really gives you a good understanding of their knowledge of pure AS3, their background, and their feelings on the state of things.

So, I’ve kept it in there. It either gives a good laugh, or a good discussion.