Philipp Rotmann wrote:
> Emile explained the down-sides quite well, as far as I
> understand -- but I think, the great opportunity of
> attracting users from every "scripting religion" ;-) that
> comes with language-independence is much more important than
> the new complexities in documentation. In fact, when
> Midgard attracts perl wizards, there will be a few among
> them who will take care of the documentation and support
> stuff, as there will be volunteers in the Python- oder
> whatever-Community. Well, they will be there to help you
> out _just after_ you made an incredible appserver for them,
> but you know that problem :-)
Being a platform for every users' favorite scripting language
is surely going to bring more developers, more people banging
on it, and is probably going to boost acceptance, documentation
and functionality. I am all for multiple scripting languages.
But we'll have to accept that most users/developers will only
see the "front-end" of Midgard, through the scripting language,
and that means we may not be able to forge ahead with new
functionality until the front-ends are in sync and stable. Unless
we make the other scripting languages 'spin-off' projects that
are allowed to trail behind the main (PHP) release. Perfectly
valid approach, but makes the others 'second-citizens'.
Bye,
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
