A vision for Parrot

[Ian Bicking]

On Tue, 2002-11-05 at 21:38, Frodo Morris wrote:
> Faster, better, cheaper.
> Imagine if parrot could understand all interpreted code.  Why not leave 
> it running, so that any Perl/Python/Tcl/Ruby/Java/sh/BASIC/whatever code 
> can get to it immediately?  A parrotd exec would consist of: "Run this." 
>   "OK".  A #! consists of "Does this file exist?"  "Yes."  "Does it 
> work?"  "Yes."  "OK, run this."  "OK".  I contend that a properly set up 
> parrotd *should* be faster than the equivalent "each language set up 
> separately" environment.

Then why not just have a libparrot?  Let the OS's caching sort it out --
if it's being used, libparrot will stay in memory.  Assuming you aren't
going to replicate OS-level functionality, like processes and memory
protection.

  Ian