From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <60bf1b7bfcbcfe2df542bb81b4ad7214@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun,  1 Feb 2009 07:56:27 -0500
To: 9fans@9fans.net
In-Reply-To: <4f34febc0901312327h2fe297bk490d3ee36faac5e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Pegasus 2.6 is released
Topicbox-Message-UUID: 907fe924-ead4-11e9-9d60-3106f5b1d025

> > the argument that if the normal extension
> > mechanism for scripting languages is x,
> > thereforenot having x is a weakness seems
> > a version of argumentum ad populum.
> >
> > doesn't dynamic loading seem at odds with the
> > tools approach?  the more complex the interface,
> > the less general the tool.
>
> Dynamic loading allows scripting languages to load arbitrary binary
> extensions at run-time.  Without dynamic loading in Plan 9 you need to
> recompile the Lua (or Python) interpreters to statically link in your
> binary extensions, so in this case dynamic loading makes the tool more
> general.  (FWIW, as has been pointed out on this list previously,
> Inferno applications can dynamically load modules at run-time.)

why do you assume that lua or whatever is not sufficient
for the task?  maybe it's the language itself that needs fixing.

otoh, my experience building websites is that i've never wanted
arbitrary functionality in the cgi.  once things got sufficiently
compliated, it made sense to build a server to manage
user sessions and whatnot.

- erik