Sure, I've got a bit of time to kill.
It really depends on the project. Based on the task in hand, I might choose from Actionscript, PHP, Javascript, C/C++, Pascal, Java, Ruby, Python, C#, Assembly (80x86, x64, PPC, ARM), Objective C. Those are all of the most common languages I work with, though more recently I have been learning Erlang, io and Go.
I agree, but conversely that doesn't necessarily make it a bad choice, if both languages are similarly capable. The language will not itself write good programs for you, it is in the hands of the engineer to write good code.
I'm not defending C++ or Pascal here. Performance alone is not necessarily a good reason for choosing a language. If performance was of paramount importance then we'd all be working in Assembly language. However, since we're not, what's the reason for that? The simple answer is that put simply, a program that takes 6 months to write in Assembly can be written in a week in a high level language such as C or Pascal. Considering the size and complexity of your average console game, you could be looking at development times that run into decades and only written by immortals.
The modern developer will often rely on the compiler to produce optimal code, but no compiler is perfect. Some careful profiling can yield a few fps boost in problem areas, but often the biggest gains are in careful choice of algorithms and data structures. Nearly all programming languages allow developers to make these choices, after all, that's their job. It is up to the engineer to write optimal code, the compiler is just a tool to help.
Well, then it's time to consider a career change![]()



Reply With Quote
The biggest advantage of having a "big toolbox" is that you can easily work together with other programmers, and have fun (which is where programming is all about 