gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnu-arch-users] Re: Re: Re: darcs vs tla


From: Matthew Palmer
Subject: [Gnu-arch-users] Re: Re: Re: darcs vs tla
Date: Fri, 12 Nov 2004 09:25:31 +1100
User-agent: Mutt/1.5.6+20040722i

On Thu, Nov 11, 2004 at 10:06:37AM -0800, Dustin Sallings wrote:
> 
> On Nov 11, 2004, at 2:09, Matthew Palmer wrote:
> 
> >Assuming equal competency in each language, it seems reasonable.  
> >There is a
> >converse, however -- higher level languages typically have more takens,
> >which means means that competency in a HLL will be lower for the same 
> >amount
> >of study effort and experience.
> 
>       I'm not sure about this.  python doesn't seem to have more reserved 
> words than C.  Then you have the special characters:   = + * / [] {} () 
> : ^ % # " """ '   (many of which are the same as many other languages).

But do those tokens do significantly more than what they do in C?  Then you
start piling the whole standard library on top, which is where a lot of the
productivity gains come from (hey, I don't have to hand-code a lot of
<whatever>, I'm so much quicker), and suddenly there's a lot more to learn
to say you're a Python guru over what you need to learn to become a C guru.

> >Andrew's comment wasn't about productivity, it was about readability 
> >and
> >maintainability.  Having seen code in a lot of languages, I agree with 
> >him
> >that programmers can make an equal mess in any language.  Touting a 
> >language
> >because it supposedly easier to write neat code will get nowt but a 
> >hollow
> >laugh from me.
> 
>       You're looking at it the wrong way.  I don't think anybody's 
> suggesting there's a language that people can't make ugly code in, but 
> it's been my experience that well-written code in a high level language 
> is far easier to read than well-written code in a lower level language.

Your standards for "well-written" just aren't high enough for the
lower-level language.

>       Or, more specifically.  It's easier to understand what five lines of 
> well written text means than twenty lines of well written text.

That's why it's easier to read Perl than C?  Because you can stuff more into
a line?  I find Perl an absolute pest to read because there's 10 ways of
stating anything, despite any size gains made from doing so.

- Matt

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]