My home language is C++ and it's where I've spent most of my time in. But here's a list of what I can remember from the past till now: C, various Basics, VB5/6, VB.NET, C#, various dBases like dBase, Clipper, McMax, 4'th Dimmension, Paradox, transact SQL on most major RDBMSs, some assembly, Javascript, some Java, Python (barely), Ruby (barely), PHP (barely), Flex (barely) and Apex/Visualforce (Force.com) is my current strong suit.
POWER BUILDER BITCHES! Just kidding. It was way too complicated

@Objective C
Damn Apple always winds up hitting the future of technology right on the nose. No, it's not Objective C per se. But the brains involved in NeXTSTEP had the right idea, imo. Objective C has a conceptually beautiful flow that is non-blocking, evented AND strongly/statically typed. This language is a natural fit for reactor patterns that produce far more scalable architectures than multi-threading could ever hope to produce.
Related slideshow:
http://www.scribd.com/doc/23801896/Node-js-JSConf-2009Reactor pattern:
http://www.cs.wustl.edu/~schmidt/PDF/reactor-siemens.pdfObjective C is ugly as hell because it's a superset of C. Anything you can compile in C will compile in Objective C. And have you
seen what you
can compile in C?

However, the right idea has to do with passing messages through your object hierarchy as opposed to pointing to an execution address and saying "do it now!" Smalltalk was like this too. The deal is that it's far more scalable to never (or hardly ever) wait for anything to finish before proceeding on to the next "request" for something to happen. This can be accomplished with most languages but is natural communication for the likes of Objective C.
Although this may sound like technobabble, as it turns out it's one of the core scaling approaches to cloud computing. You can do this in Java, Ruby, you name it. But I predict languages like Objective C will dominate in the future because of this natural fit
