ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <gip.bilotta@iol.it>
Cc: ntg-context@ntg.nl
Subject: Re[4]: Perl is evil, Smalltalk, Eiffel, Ruby, Python is the way to go!
Date: Fri, 19 Jul 2002 07:45:18 +0200	[thread overview]
Message-ID: <431961660.20020719074518@iol.it> (raw)
In-Reply-To: <87y9c92kqw.fsf@cs.uga.edu>

Thursday, July 18, 2002 Ed L Cashin wrote:

ELC> I shared your hesitations regarding Python.  When I heard about ruby
ELC> it seemed too good to be true, and I kept thinking that I wouldn't
ELC> ever prefer ruby to perl because it wouldn't have such-and-such
ELC> feature, but the more I learned about it the more impressed I was.  I
ELC> now do prefer ruby.  

ELC> While it's easy to use perl in a clean way, it's easier in ruby, and
ELC> ruby's design draws from lisp and other sophisticated languages.

A lot of Ruby say that a proficient Perl programmer (and I guess
Hans and Taco fall in this category) can grasp the core of Rupy in
one day, and 95% of it in a couple of days. So it probably
wouldn't be too hard to switch.

ELC> It would be interesting to design a new typesetting language.  :) It
ELC> should have namespaces, lexical scoping, functions/procedures,
ELC> objects, and labeled loop constructs like perl (and Java, IIRC).

ELC> These language features would eliminate a lot of the hairier
ELC> shenanighans that the ConTeXt developers have to go through in order
ELC> to do interesting things.

Well, I was thinking of Ruby as a scripting language (to obtain
texexec.rb, texutil.rb & co), but now that you make me think of it
...

TeX in Ruby? Wow, sounds interesting!

-- 
Giuseppe "Oblomov" Bilotta


  parent reply	other threads:[~2002-07-19  5:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 16:32 hi Hans Hagen
2002-07-08 23:40 ` hi Giuseppe Bilotta
2002-07-09  1:54   ` hi Glenn R. Williams
2002-07-09  7:01     ` Re[2]: hi Giuseppe Bilotta
2002-07-09  7:15   ` hi Serge Stinckwich
2002-07-09  9:26     ` hi Berend de Boer
2002-07-09  9:57       ` hi Serge Stinckwich
2002-07-09 10:14       ` hi Axel Rose
2002-07-09 10:00     ` Re[2]: hi Giuseppe Bilotta
2002-07-09 10:15       ` Serge Stinckwich
2002-07-10  8:44       ` hi Fabrice Popineau
2002-07-09 10:02   ` Perl is evil, Smalltalk, Eiffel, Ruby, Python is the way to go! Patrick Gundlach
2002-07-09 21:39     ` Giuseppe Bilotta
2002-07-09 22:19       ` Patrick Gundlach
2002-07-09 23:01         ` Re[2]: " Giuseppe Bilotta
2002-07-10  8:27           ` Hans Hagen
2002-07-10 11:49             ` Re[3]: " Giuseppe Bilotta
2002-07-18 14:06             ` Re[2]: " Ed L Cashin
2002-07-18 15:39               ` Hans Hagen
2002-07-19 15:21                 ` Ed L Cashin
2002-07-19 16:10                 ` Arun
2002-07-18 18:46               ` Johannes Hüsing
2002-07-19 15:27                 ` Ed L Cashin
2002-07-19  5:45               ` Giuseppe Bilotta [this message]
2002-07-09 23:32         ` John Culleton
2002-07-10  7:28           ` Taco Hoekwater
2002-07-10 20:44             ` Johannes Hüsing

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=431961660.20020719074518@iol.it \
    --to=gip.bilotta@iol.it \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).