Thank Serge Stinckwich. Without his video, this wouldn't have been possible.
horrido wrote
> Very cool! Thanks!!!
>
>
>
> tbrunz wrote
>> Nice!
>>
>> Here's another video, one that focuses on Roassal 3, but is still very
>> visual and does a nice job of showing what (Pharo) Smalltalk can do:
Thank you Serge! And thank you, Richard for your efforts over the years in
providing good material on Medium, Hackernoon, et al.
We need more videos like these... I just started a Slack channel where I
work (for promoting and discussing Pharo/Smalltalk), and I plan to start
posting things like t
On Tue, 29 Oct 2019 at 10:50, tbrunz wrote:
> Thank you Serge! And thank you, Richard for your efforts over the years in
> providing good material on Medium, Hackernoon, et al.
>
> We need more videos like these... I just started a Slack channel where I
> work (for promoting and discussing Phar
very nice.
I have noticed that linked youtube videos have less likes than
positive responses here. Liking them on youtube could help a bit for
youtube algorithm to appreciate them slightly more.
davorin rusevljan
On Tue, Oct 29, 2019 at 5:25 PM Christopher Fuhrman <
christopher.fuhr...@etsmtl.c
--- Begin Message ---
Hello,
I have to made this challenge as last on of the OOP book
Servers answering requests
When a server node consumes a
packet, it converts the payload to uppercase,
then sends that back to the sender of the request.
The first question you should ask is "What do I expect #ball asUppercase to be?"
The ANSI Smalltalk standard says
5.7.10.9 Message: asUppercase
Synopsis
Answer a new string which contains all of the elements of the
receiver converted to their upper
case equivalents.
Definition:
Answer a new s
--- Begin Message ---
Thanks,
That part I understand but what I try to say is that if I understand
the code right the string BALL is send back to the node that send the
orginal messsgae #ball. But as I said that one do not seem to recieve
any packages and my question is still why ?
I deb
