Linked by Thom Holwerda on Wed 11th Apr 2007 16:35 UTC, submitted by ShlomiFish
General Development "What makes programming languages are suitable or unsuitable as introductory languages? Which languages are better learnt first and at which order? And why what the masses think is the most suitable introductory programming language is not in fact that. This paper examines several approaches to which programming language is the best, and afterwards gives several useful relations for which languages should come first. Finally it gives a final verdict, defends it and then gives some other good food for thought."
Permalink for comment 229646
To read all comments associated with this story, please click here.
by jack_perry on Wed 11th Apr 2007 18:39 UTC
Member since:

I haven't learned Python or Ruby yet; I have the book on Python cited above, and it does look good, although I think I need something higher-level (so if anyone can recommend something, let me know). I have worked with Perl, and IMHO it was a sharp wit who observed that Perl was the first "Write Once, Read Never" language. (Although perhaps not the first, considering APL.)

I learned to program in Pascal, and I liked it but the original language is a bit dated. BASIC is even more dated.

Personally, I like Eiffel. It has the readability of Pascal, the clean design of a pure object-oriented language, a speed comparable to C (although the memory requirements tend to be higher), and a Design-by-Contract philosophy that in my experience works beautifully. It isn't just a language; it a method for software engineering. There is "one way" encouraged to write Eiffel programs, although Eiffelists don't seem as restrictive as "the Python way".

Sadly, the two major Eiffel camps have forked (ISE Eiffel and SmartEiffel) and both compilers seem to be in transition, but I very much like both dialects.

Reply Score: 2