Quote:
|
Originally Posted by Nodrog
its too low-level, you will spend too much time fighting against stupid syntax and machine level stuff rather than learning proper programming concepts.C++ is only a useful language when your code has to run extremely fast, and for 99% of applications speed isnt the primary issue. If youre serious about programming then its important to learn C at some point to get an understanding of whats actually going on inside your computer, but theres really no benefit in learning C++ unless you either envision a career which requires you to do it, or are working on some very niche low level things (modern 3d games, integrated circuits, etc).
|
You are mistaking C++ with C. And I would always expose people to C / Assembler first (or at least very early on) to teach them how a computer really works*. Then we can shift on and explain about abstract concepts like double linked lists, sorting algorithms and so on.
Quote:
|
Originally Posted by Nodrog
Its a terrible first-language to learn at any rate, because all the important concepts get obscured by the pathologies of the language and youll just end up fighting with C++ rather than actually learning general programming skills.
|
C++ is certainly no worse to learn than Java. Granted, you have added payload of taking care about your memory management, but in the end that is something every programmer should know about. C++ is by default not obscuring anything, even though it can be used to write fairly obfuscating code (template meta programming <3). But just because the language allows you to do something it does not necessarily mean that you should use it right from the start. There is a correct time and place for everything.
I do, however, agree that in the end it is more boiling down to what one wants to achieve first. There is no absolute right, nor total wrong when it comes to learning a programming language, it all just depends upon your goals.
Want to develop ordinary applications? Go with Java / C# / C++.
Want to do some funny scientific stuff? Go Haskell / Python and the likes.
Want to push hardware to its real limits? Go C / ASM, and make sure you get good understand of the operating system and hardware of your targetted device.
Or do it like Knuth and use some fictional architecture to not have such stupid discussions about programming languages :-)
*Especially because it shows that a computer's resources are actually fairly limited, and that a computer is only good at following your instructions.