All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

Do you think there are language features which encourage more respect for OOAD in Java versus Perl? Do you think the way that people approach and learn both languages lead to different types of programming?

(I ask because I suspect that there's one strong trend involved, but I'd like to hear your thoughts here, if the questions are at all interesting to you.)

Hi chromatic,I was thinking of emailing you to suggest plugging perlsurvey.org.

"Do you think there are language features which encourage more respect for OOAD in Java versus Perl?"

In some regards. The language, by design, treats it as important, so it encourages respect. And you'd have to have some respect for it to use the language, or be willing to learn respect for it, or else be willing to put up with a lot of pointless fuss for no good reason. The language itself doesn't help you with OODA, but the

Java ended up as the de facto teaching language because Pascal was the teaching language of the previous generation, C++ was too baroque, Smalltalk was too much unlike Pascal, and when "How to Use Excel" is a CS class, there's no way you can think about teaching undergraduates Scheme.

Though there were still a few books written about Smalltalk or Lisp in this era, non-theoretical CS programs moved to Java in the late '90s, hence Design Patterns mixed C++ and Java examples (and