t 1:19:53 PM, Andrus Adamchik (and...@objectstyle.org)
> wrote:
>
>> > I tried to follow the threads but soon got lost. I strongly suggest that
>> > such technical issues MUST NOT be discussed on Slack but must be CARRIED
>> > OUT ON THE MAILING LIST. Slack is not sear
October 20, 2016 at 1:19:53 PM, Andrus Adamchik (and...@objectstyle.org)
wrote:
> I tried to follow the threads but soon got lost. I strongly suggest that such
> technical issues MUST NOT be discussed on Slack but must be CARRIED OUT ON
> THE MAILING LIST. Slack is not searchable, the th
> I tried to follow the threads but soon got lost. I strongly suggest that such
> technical issues MUST NOT be discussed on Slack but must be CARRIED OUT ON
> THE MAILING LIST. Slack is not searchable, the threads are not followable,
> Google does not index Slack discussions (as f
... a complete waste (at least for me).
Slack is great for chit-chat but not for anything seriously technical. Here is
an example:
There was a message from josefv on October 5th with a question about object
qualification during a fetch. This question resulted in a very interesting
technical
