13 Nov
2015
13 Nov
'15
8:46 p.m.
Nice.
On 12/11/15 23:51, Dimitris Chloupis wrote:
I am kinda suprised that Roassal is not included with
the Pharo image,
looks to me like something Pharo could easily take great advantage of
to extend its visual coding style.
There are two opposing forces at work here: In the development
environment we want very rich tools. In production, we want to be able
to work with as little baggage as possible. So Pharo is moving towards
as much externally loadable code as possible, getting to a pharo-kernel.
When the tools are able to support remote editing and debugging, we can
have many pharo-kernel images controlled by one big development
environment.
Stephan