[squeak-dev] SecureSqueak

Michael van der Gulik mikevdg at gmail.com
Thu Mar 18 21:23:27 UTC 2010

On Fri, Mar 19, 2010 at 4:25 AM, Ralph Johnson <johnson at cs.uiuc.edu> wrote:
> In my opinion, if you want to grab some code off the internet and run
> it in a sandbox, you should spawn a slave image and run it inside that
> image.  The VM should ensure that any important requests have to go
> through the master image.
> In the same way, Croquet really ought to run each island as a separate
> image.  The UI ought to be able to look into each island to display
> it.  This would make it easy to prvent cross-island references.
> Similarly, the way to write parallel programs is to spawn an image for
> each core. In general, a single image should be a single process.  It
> should be easy to develop an application that consists of a set of
> images.

You could do it that way. You'd have a different set of issues to work
through though, such as inter-image communication.

As with concurrency, I think time is much better spent improving
support for the concurrency that we already have: green threads on a
single CPU core. The debugger, scheduler, and UI could all be
improved. There's no point in making the VM able to use multiple cores
unless we actually have concurrent code to run and problems to solve.



More information about the Squeak-dev mailing list