Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

What is a good first language?

Name: Anonymous 2009-03-06 16:45

My 20 year old brother wants to get into programming.  I want to set him up with a language that has these features:

1. Easy to learn, must have simple syntax
2. Immediate results, easy to make graphical and text outputs.
3. Fully featured language(I want him to be able to easily progress into more advanced stuff and not be limited by the language)
4. Fast(So he gets the idea of how powerful computers are)

Name: Anonymous 2009-03-07 13:18

>>50
You are still wrong. Hand coded assembly for trivial programs will still be slower than optimized c/c++ if the assembly is written by a non-expert assembly programmer.  You obviously know very little about assembly or compiler optimization.

Name: Anonymous 2009-03-07 13:35

I'm not >>50 but something tells me you haven't coded much in assembly. I've seen plenty of x86 asm apps which are faster than their C equivalent(not to mention that not all optimizing compilers are created equal, and that it's always possible to make a better optimizing compiler), and in most cases can code something faster than what my compiler produced for a piece of C code (It's rarely worth my time for me to be wasting time hand optimizing something in asm unless it's truly time critical). Here's another example: have your compiler generate the assembly for some complex computationally expensive function, then just try to see what you can optimize in the generated code, in many cases you'll find out you could rewrite certain code to be much faster than the code your compiler generated, this is because a human who can think in the context of the code and knows his asm can almost always find better way to solve a specific problem, unlike a compiler whose algos are designed to generate code which works commonly faster in generic cases.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List