rondogw wrote:That's pretty cool.
Wow.. How many programming languages do you know?
After awhile, the language becomes more or less just syntax, and you can always get a QRC for that. What's important is the overarching design and logic structure the language was made to support.
I class them in five buckets ::
Machine languages (pure procedural)
Structured programming languages (C, ADA, APL, COBOL SNOBOL, Fortran, Basic,and a cast of thousands) and scripting languages, other than Python, Ruby, etc. I also include the macro laguages like CICS here. (complex procedural)
C++, Java, C#, Smalltalk, Lisp and scripting languages like Python, and Ruby (Object oriented, nonprocedural languages
Haskell, IPL, and other functional languages (next wave, get on Haskell and the whole paradigm while it's hot)
I've programmed in all of the above and a whole lot of unnamed suspects.
See, if you know the structure the language supports and can think in it to do your design, the only relevance is that the language fit the structure.
In the beginning, it feels like there are a lot to learn, but in the end, they are all the same building blocks -- reference, addressing, arithmetic functions, type casting and conversion, loops and control structures and I/O support.
Some are really different.
I'd recommend Java, Ruby or Python, and Haskell as beginning languages now.