One quick clarification, if you would be so kind. Isn't it true that even
after the image file is loaded there is still an interpreter present (as with
Forth) that can permit subsequent interpretation of new stuff even if
everything in the image file has already been compiled?
> Date: Fri, 9 Sep 2011 10:10:15 -0700
> From: [email protected]
> To: [email protected]
> Subject: Re: [Factor-talk] Mixed up about deployment
>
> Hi Patrick,
>
> On Fri, Sep 9, 2011 at 5:22 AM, Patrick Mc(avery
> <[email protected]> wrote:
> > With factor, what is happening during deployment? Is there an
> > interpreter built into it's own executable like py2exe? :
> > http://www.py2exe.org/
>
> When you run the Factor VM binary named 'factor', it loads an image
> file named 'factor.image'. Similarly, when you use the deploy tool to
> deploy your app, it creates an image file named 'myapp.image', and
> copies the VM binary to a new binary named 'myapp'.
>
> > I don't know much about smalltalk, are there any downfalls to this
> > approach? does it mean heavier memory use at runtime? is there more
> > redundancy between files compared to files being sent to a separate
> > interpreter at runtime like Lua? Disk spaces is almost irrelevant now
> > but it would still be good to know. If several instances of the same
> > program were running at the same time would there be memory waste vs the
> > other approaches?
>
> A good way of thinking about the image is that it is a cache for
> parsed and compiled code that just happens to be serializable to disk.
> While Factor does use more memory than Lua for various reasons, it is
> not anything inherent in the image model. Lua has the same data
> structures in memory after you load a source file -- syntax trees,
> bytecode, and JITted code. It just doesn't offer a way of saving them
> to disk, so you "deploy" by giving your users the source code and an
> interpreter, instead of an image file and a VM.
>
> Cheers,
>
> Slava
>
> ------------------------------------------------------------------------------
> Why Cloud-Based Security and Archiving Make Sense
> Osterman Research conducted this study that outlines how and why cloud
> computing security and archiving is rapidly being adopted across the IT
> space for its ease of implementation, lower cost, and increased
> reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/
> _______________________________________________
> Factor-talk mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/factor-talk
------------------------------------------------------------------------------
Why Cloud-Based Security and Archiving Make Sense
Osterman Research conducted this study that outlines how and why cloud
computing security and archiving is rapidly being adopted across the IT
space for its ease of implementation, lower cost, and increased
reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
