Whoa Whoa, let's back off a second here... Koopsta says "I want to start learning how to program..." not "I want to make a profession of programming...".
If any soul wants to make a profession of programming, then they can go to school and learn like everyone else. There, they will get a full taste for the whole gamut of languages. I've done Assembly (68k and RISC), C, C++, Java, VB6, Access (& VBA), Prolog, J (an APL descendant), T-SQL, Javascript (or JScript), VBScript and of course, .NET Languages (C# and VB). And I still don't recommend any but the big three (Java, C#, VB.NET) to dabblers and enthusiasts.
Comments about
rigidity and
structure, are really just junk in the .NET era. C# and VB.NET are nearly identically functional languages (this was not the case with VB6). With an IDE in front of them there is no difference in rigidity or "nitpickiness", they are interfacing with the same .NET Assemblies and the syntax checker saves you either way.
You state that
Quote:
Another reason to learn "legacy" languages like C/C++ is because they are the standard for almost all languages out there. I learned C++ first..
Which is really incomplete logic. I mean if it was
good to learn C++ first, then why not learn C first? Wouldn't that be
better? Heck why don't we just start all newbies at Assembly code? That would be
the best. Because then when they "get a job in
RISC development" they'll get paid more than the C#, the Java
and the C++ programmers? Hey ,why not just teach them RPG and move them right to the top of the niche-market pay scale?
All of these languages (except RPG) are
Quote:
standards for almost all languages out there
, but I'm not going to walk in to my computer programming night course and show my 101 students the
wonders of coding in 68k.
Newbies and enthusiasts want results for their time and .NET / Java, deliver those results with a minimum of hassle, time and learning curve.
Let them drive automatic for a while and if they really like it, then I'll show them how to drive stick.