Which other languages compliment AS3/flash?

Question

So, i've been learning some flash and AS3 recently as part of my job and i plan on learning some more.
I have another project starting soon (the details of which i've posted at the bottom but aren't necessarilly relevant for this discussion*).
Basically the jist is, i'm looking at learning another language and i was wondering which direction to go, what languages could be used in developing good flash applications or what languages would cover projects that flash was irrelevant for. What other languages have people gone on to learn after learning actionscript and how were they helpful? I've done a little research and found http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html in my opinion it's only worth learning something that other people are still using and that employers might consider a useful skill.
*future project details:
I have a physics simulation package that essentially outputs text files in the form of:
Generic time stamp
Next time stamp
and it goes on and on and on like that for potentially thousands of cycles- where hashes are numbers that correspond to density of a molecule at that position in a square. The grid size will vary depending on what i tell the simulation to do. (it's 5x5 now but it could be 10x10 etc)
There are a number of these output files created each time the simulation is run and each file corrosponds to the density of a different atom.
A good starting point for me would be to create a program (with an easy gui for others to use) that allowed a user to specify which of the atoms densities he wants to view and pick a start and end time and then watch a movie (essentially a slide show) of the density changing over this time. Where the density would be colour coded in some way.
Matlab has been suggested, but i'd much rather improve my coding skills by learning something more relevant to non-scientific tasks.

Answer 1

Speaking as a developer who has built and worked on a number of large-scale apps for long-term clients; you would need to shoot me and prise the Flex framework from my cold, dead hands before I would give it all up in favour of the huge limitations of a pure AS implementation.
Yes, it is possible to build bad, slow, heavy Flex AIR apps. Yes, it is possible to build faster, slicker, lighter pure AS apps.
But...
Once an app is out there, you need to maintain it.
And...
If you build the thing properly in the first place, performance will be comparable or better using the well-defined systems and frameworks of Flex / AIR.
Or rather...
There are things that it is better to build your own controls for than to use Flex's ones, but those things are so few and far between, and so obvious after just a little bit of performance testing, that it is almost always going to be preferable to build using Flex default and then to replace the problem items _and_only_ the problem items with home-cooked controls that _are_integrated_ with the existing Flex framework.
G