Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

gnat (29)

  (email not shown publicly)

Journal of gnat (29)

Monday May 19, 2003
09:27 PM

Family Tree of Programming Languages

[ #12318 ]
This poster of languages seems a little fictitious when it comes to our own favourite. No Perl 5? Ruby isn't descended from Perl? Perl's not descended from C?


The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • "A hardware description language"?
    But yes, the chart seems to be somewhat, err, tilted.
  • They missed the sed -> Perl, Smalltalk -> [Ruby, Perl] (not sure if that's direct though), CLU -> Ruby and am I right in not seeing Logo or Turtle Graphics *anywhere*?

    I like that Perl 1.00 is considered to be "Active, Thousands of Users".
    • I.Other Languages.

      Turtle Graphics is there, the Logo line branches off LISP quite early.

      Majority of Lisp and Fortran dialects ignored; Watfor, Watfiv. Scheme fed back into CL. Isn't ML related to Lisp and Haskell? Prolog was spawned by Lisp.

      Addendum on PL/1: it included features of Lisp with Cobol and Fortran, with the syntax of Algol.

      Ruby folks seem to say Ruby is Perl with SmallTalks real-OO, with Python and Lisp mixed in to.

      Python specifically names Perl as Anti-influence and claims Lisp heritage.


      # I had a sig when sigs were cool
      use Sig;
      • Point of order. Ruby existed before Perl 5, though it was late 1995 before Matz publicly released it. He also claims Python influences.

        I knew Python then. But I didn't like it, because I didn't think it was a true object-oriented language. OO features are appeared to be add-on to the language.
        --Matz []

        I'd make it more like (Python 1, Perl4, Smalltalk) -> Ruby though I'm not even sure Matz knew much Smalltalk at the time.

  • to be most polite, indeed.

    Besides the question of omissions and missing/questionable lines of heritage, there are also such "forward-looking" statements as referring to C#'s staying power. Indeed, referring to either C# or Java as "classic" seems a little presumptious.