Hi Norbert,
Le lun. 1 oct. 2018 à 19:22, Norbert Hartl a écrit :
>
>
> Am 26.09.2018 um 19:22 schrieb Nicolas Cellier <
> nicolas.cellier.aka.n...@gmail.com>:
>
> Very nice proof that we can leverage efficient and up to date technologies
> !
>
>
> That was part of the plan ;)
>
> Thank you so
> Am 30.09.2018 um 13:01 schrieb Pierce Ng :
>
> On Wed, Sep 26, 2018 at 07:49:10PM +0200, Norbert Hartl wrote:
And a lot more. This is a coarse grained overview over the
architecture. I’m happy to answer further questions about this.
[very nice writeup]
>
> Hi Norbert,
>
>
> Am 26.09.2018 um 19:22 schrieb Nicolas Cellier
> :
>
> Very nice proof that we can leverage efficient and up to date technologies !
That was part of the plan ;)
> Thank you so much for sharing, that's the right way to make Pharo (and
> Smalltalk) alive and kicking. How did the Pharo IDE
On Wed, Sep 26, 2018 at 07:49:10PM +0200, Norbert Hartl wrote:
>>> And a lot more. This is a coarse grained overview over the
>>> architecture. I’m happy to answer further questions about this.
>>> [very nice writeup]
Hi Norbert,
Very nice write-up, thanks.
What persistence mechanism are you
> Am 25.09.2018 um 17:44 schrieb Sven Van Caekenberghe :
>
>
>
>> On 25 Sep 2018, at 14:39, Norbert Hartl wrote:
>>
>>
>>
>>> Am 25.09.2018 um 12:52 schrieb Sven Van Caekenberghe :
>>>
>>> Wow. Very nice, well done.
>>>
>>> Any chance on some more technical details, as in what
Very nice proof that we can leverage efficient and up to date technologies !
Thank you so much for sharing, that's the right way to make Pharo (and
Smalltalk) alive and kicking. How did the Pharo IDE help in such context?
(did you use debugging facility extensively?).
What tool is missing?
Le
> On 25 Sep 2018, at 14:39, Norbert Hartl wrote:
>
>
>
>> Am 25.09.2018 um 12:52 schrieb Sven Van Caekenberghe :
>>
>> Wow. Very nice, well done.
>>
>> Any chance on some more technical details, as in what 'connected by a
>> message queue for the communication' exactly means ? How did