Pharo-min?

> I'm interested in building a minimum image from a Pharo-core base.  This
> image would have:
>
> - no GUI/mouse/keyboard.  The only interface would be via network connections.
>
> - no processes/interrupts.  The network send/receive would be synchronous via a plugin.
>
> - no timer.  The date/time would be via a plugin on demand.
>
> - no fallback debugger.  Any error fallback would log a message and abort via a plugin.
>
> - possibly a minimal interpreter that didn't include any support for
> those unavailable features.  (The only value in this would be smaller
> size and hopefully something more comprehensible for code auditing
> purposes.)

> [hidden email] wrote:
>
>> I'm interested in building a minimum image from a Pharo-core base.  This
>> image would have:
>>
>> - no GUI/mouse/keyboard.  The only interface would be via network
>> connections.
>>
>> - no processes/interrupts.  The network send/receive would be synchronous
>> via a plugin.
>>
>> - no timer.  The date/time would be via a plugin on demand.
>>
>> - no fallback debugger.  Any error fallback would log a message and abort
>> via a plugin.
>>
>> - possibly a minimal interpreter that didn't include any support for
>> those unavailable features.  (The only value in this would be smaller
>> size and hopefully something more comprehensible for code auditing
>> purposes.)
>
> Part of this is already covered by Pavel's minimal morphic/image work.
>
> - no timer
> there is a difference between date/time and the delay/timing framework
> in the VM. Removing the latter could be "interesting"
>
> Everything else you could basically do by creating new Socket classes,
> changing default error handling etc.
> Although I'm not quite sure what you would gain from not using the green
> threads in Squeak/Pharo?
>
>
> Michael
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 

> Sorry if this is seen as off-topic, as I realize the goal is to get
> Pharo-1.0 out the door, but I'm evaluating Pharo as the base for a
> potentially huge application.
>
> I'm interested in building a minimum image from a Pharo-core base.  
> This
> image would have:
>
> - no GUI/mouse/keyboard.  The only interface would be via network  
> connections.
>
> - no processes/interrupts.  The network send/receive would be  
> synchronous via a plugin.
>
> - no timer.  The date/time would be via a plugin on demand.
>
> - no fallback debugger.  Any error fallback would log a message and  
> abort via a plugin.
>
> - possibly a minimal interpreter that didn't include any support for
> those unavailable features.  (The only value in this would be smaller
> size and hopefully something more comprehensible for code auditing
> purposes.)
>
> Why bother with Squeak/Pharo/Smalltalk at all, some may ask?  I need a
> very reliable, *very* efficient, *very* powerful deployment platform,
> and at the same time a *very* powerful development environment so we  
> can
> stay nimble.  The proposed alternative is Java, which meets the points
> except on efficiency and development fronts.  I've also been  
> involved in
> a somewhat similar-scale project in the past, but the overwhelm of  
> 100+k
> lines of Java code really bogged us down in the end.  I'll look at GNU
> Smalltalk too, for deployment, but I'd *really* like to be running the
> identical code in development, test and production.
>
> Any gotchas?  Any suggestions/hints?
>
> Just to tweak your interest further, the deployment platform would be
> z/OS running on IBM big iron!
>
> ../Dave
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>