From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4f34febc0805012139h64d04e8ck37eda05522802906@mail.gmail.com>
Date: Thu,  1 May 2008 21:39:31 -0700
From: "John Barham" <jbarham@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <7359f0490805011852k64a52a01k1efc1e6aba8b030c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3CB4093E-098C-4E6F-B843-7B65E4461D81@mac.com>
	<7359f0490805011852k64a52a01k1efc1e6aba8b030c@mail.gmail.com>
Subject: Re: [9fans] A new language for Plan 9
Topicbox-Message-UUID: 9c846016-ead3-11e9-9d60-3106f5b1d025

Rob Pike wrote:

>  I have lots of other examples of lesser disasters. As code grows,
>  white space indentation becomes ever more problematic. It's a
>  maintenance disaster.

I beg to differ, at least when it comes to my experience working w/
Python.  I work day in and day out on a 50,000+ line Python
application and can't recall a single bug that was caused by
whitespace indentation.  But granted Python is better hand-written
than generated...

Working on a constantly moving code-base I've experienced more
problems due to Python's dynamic typing, but that's a double-edged
sword and on balance it's still a big plus.

  John