YayPython wrote:Oh god...Sorry to crash the party, but the size of the framework is a HUGE turnoff for me...
Haha, very true. I personally enjoy writing very small code.. Small PE's and assemblies make me happy :]
Really, when it comes down to it, it's all about the application of your, er, application. Are you writing code for an ATmega168? You only have a program space of 16KB, with 1KB of RAM and a 16MHz processor. You probably
won't be using the .NET framework, or a Java VM, even if they were designed for embedded hardware (.NETCF or MIDP). Enjoy your C.
Are you writing an installer for the application you wrote last night for quick distribution? Why not use a RAD tool so you can get it out the door faster? There is no reason to spend forty extra hours of development to implement it in C++.
Are you writing a pixel shader for the new game you are developing? That probably won't be in a managed language.. I'd like to see one try! But you can probably afford some higher level libraries, such as file streams, etc..
That backup script you run nightly to pull down databases from your live server probably isn't written in any of the above; it's most likely a bash script.
Each language has its pros and it's cons, but it goes beyond that. Each language has its pros and cons per application, and knowing what languages are meant for is just another part of programming. I see you like Python :]