Ask a Question related to Ruby, Design and Development.
-
james_b #1
[PYTHON] YAPVRA (Yet Another Python vs. Ruby Article)
Interesting blog post from a Pythonista on "Linguistic Simplicity," and
why Ruby fails to pass muster.
[url]http://toulouse.amber.org/archives/2003/08/21/linguistic_simplicity.html[/url]
And, please, this is not an invitation to a flame war or general
grousing. Read it to see how others perceive Ruby. If you think the
author has misrepresented something, post a polite comment to his blog.
(And if you think the preceding comments were obvious, then my apologies.)
James
james_b Guest
-
ruby from python
hi, while is well known how to call python from ruby I would like to do the reverse. Have you some informations or hints ? -
Ruby vs Python?
Hi all, Could someone offer me a comparison between Ruby and Python? Me and one other person are thinking of starting a project and we haven't... -
OOP flavours - was Python vs. Ruby
On Wed, 3 Sep 2003 09:33:02 +0900 David Naseby <david.naseby@eonesolutions.com.au> wrote: <snip> <snip> Actually this isn't a very good... -
OOP flavors - was Python vs. Ruby
I think you have to recognise that there are different views of the objects, depending on what level or abstraction you are working on. Take,... -
Python vs. Ruby
Can anyone give me a good reason why I would want to use Ruby over Python? Does Ruby has any inherent advantages over Python? The reason I ask is... -
Ben Giddings #2
Re: [PYTHON] YAPVRA (Yet Another Python vs. Ruby Article)
On Saturday, August 23, 2003, at 02:04 PM, james_b wrote:
Python users are always harping on how in Python code looks the same,> Interesting blog post from a Pythonista on "Linguistic Simplicity,"
> and why Ruby fails to pass muster.
no matter who writes it, because a fundamental design decision for
Python is that there should only be one way of doing something. But
that simply isn't true, even with the most basic of features, "import"
1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987>>> import fibo
>>> fibo.fib(1000)
1 1 2 3 5 8 13 21 34 55 89 144 233 377>>> from fibo import fib
>>> fib(500)
1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987>>> import fibo as foobar
>>> foobar.fib(1000)
1 1 2 3 5 8 13 21 34 55 89 144>>> from fibo import fib as bif
>>> bif(200)
As for the rest of his entry, it's mostly flamebait. Perhaps
unintentional, but he misrepresents certain aspects of Ruby. He
prefers the syntax of Python to that of Ruby. Fine. He doesn't get
that conditional expressions could be designed to return values. Fine.
My reasons for disliking Python are mostly personal too. I happen not
to like too many underscores. I dislike explicitly passing "self" to
methods in a supposedly object-oriented language. (Incidentally, the
same thing I dislike about Perl's OO syntax, and Ruby is supposed to be
the one that's more Perl-like).
The most common complaint I've heard about Ruby from Python people is
that there's more than one way of doing something, and there are
strange shortcuts and Perl like special variables around. There's
something they don't seem to realize (and what you wouldn't realize
unless you spent some time with Ruby). Although there's more than one
way to do things, there's the path of least resistance, and everybody
seems to follow it. Sure, $_ exists, but nobody seems to use it,
because the places it is mostly used in Perl are done with iterators in
Ruby.
What's funny is that from his page he links to a post he made in
comp.lang.python about his experiences with Ruby, and that post was
made in response to a post by "Brandon J. Van Every", asking "What's
***TOTALLY COMPELLING*** about Ruby over Python?"
Ben
Ben Giddings Guest



Reply With Quote

