[Mono-devel-list] PHP and mono

Robert Hostetter robert.hostetter at gmail.com
Wed Oct 13 11:23:57 EDT 2004

Why target parrot as many are talking about PHP doing in the future? 
Wouldn't mono be more ideal?  If all the P languages (Python, PHP, and
Perl) targetted mono the energy could be devoted to a common
infrastructure (mod_mono).  Also currently PHP throws away the
compiled bytecodes (unless you invest in the Zend cache or use one of
the not-heavily-maintained cachers.)  APC and Turck MMCache have very
little development activity, and the maintainer of Turck was recently
hired by Zend and he therefore discontinued development.  By using a
common runtime the compilation results of the JIT could be cached and
all languages would benefit.  Additionally easy use of PHP in other
mono languages and vice versa would be a benefit (a major reason why
people want to move to Parrot).  Lastly if Ironpython can do it and be
fast (although apparently the author found a few bugs in Mono that
caused a major slowdown) why can't PHP?  These were my thoughts
anyway.  I just don't understand why create yet another platform
(parrot) when mono has already been created.

God Bless,
Robert Hostetter

On Wed, 13 Oct 2004 16:45:38 +0200, Andrea Colanicchia
<andrea.colanicchia at gmail.com> wrote:
> On Wed, 13 Oct 2004 09:48:19 -0400, Robert Hostetter
> <robert.hostetter at gmail.com> wrote:
> > Is anyone currently working on implementing PHP in mono?
> I don't know, but exists an extension in PHP to use mono assemblies:
> http://www.php.net/~sterling/mono/
> Bye, Andrea.

More information about the Mono-devel-list mailing list