From: Tomasz Wegrzanowski <taw@...>
Date: 2002-01-01T05:25:58+09:00
Subject: [ruby-talk:29889] Re: Ruby/Python: Software Engineering

On Tue, Jan 01, 2002 at 05:03:35AM +0900, noone wrote:
> All:
> 
> There are many things I like about Python, but the one that seems to keep me w/ Python
> is (IMHO) its commitment to "software engineering practices/methodologies".
> 
> Hopefully staying away from an infinite recursive descent into definitions,
> is there any good summary that attempts to justify where/how Ruby makes this a priority?
> 
>   Quentin Crain
> 
> What follows is detail which is not necessary to answer the question above, but fills out (a little) my thinking.
> 
> Software Engineering Practices/Methodologies include:
> 
>   Designed from the "ground up" for readability
> 
>     Enforced indention (you indent your own code I bet)
>     { @No #line $noise }
>     No short cuts ($!, $%, etc)
> 
>   Documentation a priority from the beginning
> 
>     docstrings (at all)
>     docstrings (as properties)
> 
> Many of you are probably tired of this type of thread, but these are the types of things that keep
> me using Python and I am wondering if/when/where Ruby addresses them. Are these simply topics of opinion,
> or do they actually matter?

Ruby doesn't do things you want and we should thank Matz it doesn't.

Enforcement of indentation, lack of what you call "line noise" and lack of short cuts
have very little to do with quality of software.

Nobody will try to force you to switch from Python to Ruby.