In article <[EMAIL PROTECTED]>,
Alex Martelli <[EMAIL PROTECTED]> wrote:
.
[much valuable and
correct detail that
somehow managed to
avoid mentioning
Forth or Smalltalk]
.
.
>Despite the many differences of detail (mostly, though not exclusively,
>details of "syntax sugar"), I consider Ruby and Python to be essentially
>equivalent *as languages*, so I would suggest you choose on a strictly
>pragmatical basis -- quality of framework and library, execution speed,
>tools, books, third-party extensions, &c. I see it as a tribute to both
.
.
.
I think it's worth repeating, Alex, a point you've made in the
past, and that tangentially supports your elided example about
"c = d unless ...": it's possible to distinguish Python from
Ruby in another way. Python is arguably better for group work,
or at least more standard for team projects, because it more
consistently exposes "one correct solution", while Ruby both
admits more stylistic variation, *and* encourages construction
of novel control structures.
--
http://mail.python.org/mailman/listinfo/python-list
