From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] tcl, 9p
Date: Sun, 9 Oct 2011 09:12:25 -0400 [thread overview]
Message-ID: <7181f649ff38e68cc8bcabb1fa40df94@chula.quanstro.net> (raw)
In-Reply-To: <CAOe8CcYL4J5Uu4MSwpT8bO=4LC7omJ84FDkRy=ZXzq8wNH5iWg@mail.gmail.c>
On Sun Oct 9 02:16:11 EDT 2011, pmarin.mail@gmail.com wrote:
> In 15 years Tcl has been improved a lot, like any other language.
that might not be relevant to ron's point. i think this is almost
a geometry problem. if you plot languages in 1997 and late 2011 on the
"goodness line", it should follow that improving isn't enough to have
a sufficiently large "goodness factor". the language in question has to
be improving fast enough relative to the competition to be in the top
bunch (largest x). if you only plot languages similar to tcl on this line,
i think you get the same result.
in tcl's case, the segment between starting point and today would seem
to need to be prohibitively long. (although python made the minimum
segment length much shorter by making python 3 incompatable with 2.)
- erik
next prev parent reply other threads:[~2011-10-09 13:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 0:02 L N
2011-10-09 2:31 ` Russ Cox
2011-10-09 3:20 ` L N
2011-10-09 3:30 ` Venkatesh Srinivas
2011-10-10 9:05 ` Balwinder S Dheeman
2011-10-10 13:33 ` Paul Lalonde
2011-10-10 13:51 ` simon softnet
2011-10-10 16:57 ` Wes Kussmaul
2011-10-11 7:50 ` hiro
2011-10-11 8:34 ` L N
[not found] ` <CAFUsep0WRifUREf=BuX2hMT85g46pObH-3Q6XFcf82ONOGTeEw@mail.gmail.c>
2011-10-10 21:16 ` erik quanstrom
2011-10-26 16:45 ` Balwinder S Dheeman
2011-10-09 5:21 ` ron minnich
2011-10-09 6:15 ` pmarin
[not found] ` <CAOe8CcYL4J5Uu4MSwpT8bO=4LC7omJ84FDkRy=ZXzq8wNH5iWg@mail.gmail.c>
2011-10-09 13:12 ` erik quanstrom [this message]
2011-10-09 17:24 ` simon softnet
2011-10-09 23:05 ` Nick LaForge
2011-10-27 7:46 ` Axel Belinfante
2011-10-10 20:55 Winston Kodogo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7181f649ff38e68cc8bcabb1fa40df94@chula.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).