Uh-oh... language wars!

Ooops, the inevitable started...

But Pascal, I totally agree with you. In the end, I really think it all comes back to having those fundamental skills, which I what I was trying to get across unsuccessfully in my first few posts (and something I alluded to in my post about "Java bigotry"). If you understand the concepts involved with designing and developing an application and the basic tenets of computer science, it doesn't matter what language or technology you're working with.

I went to a small liberal arts college, majoring in Computer Science. The curriculum was heavy in abstract theory and whatnot. In fact, I had two courses over my four years there that focused solely on languages, their classifications and design, and how to learn new languages. That's the liberals arts mantra - "learn how to learn".

I learned in Java and C++. I've worked with everything from JScript (don't laugh - we did some pretty crazy things with object-oriented JScript!) to VB to XSLT (which I consider a language) to C# since. I've always thought that the single best thing I bring to the table is my ability to learn new technologies.  

Also, though, we really don't have much choice from project to project. In our "enterprise development" here, we've standardized on a language and platform (for reasons such as maintainability and "standardizing" the skillset, among others). We did decide on C# though, and not VB.NET, which is somewhat interesting considering we were primarily a VB shop before this...

I'd also like to point out whether I agree or not probably has little relevance, since Pascal has been programming for as long as I've been alive... :)

EngineeringWriting