... 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 discussion on how to solve the problem. hugi and samuel chimed in and presented a solution including great background info. The discussion was interrupted by unrelated messages and another technical question. 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 far as I know). And most of all the discussion thread is not easily archived. Any mailinglist posting defines a discussion thread that can be followed and archived. I often remember that there was some discussion about an issue I have during my work and most of the time I can find the relevant messages in my mail archive. What do others think? Is it just me? I may not understand properly how to work with Slack. If that's the case, fine, please enlighten me. Long live WO ! (yes, I know, but.... anyway. Long live WO ! ) ---markus--- _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
