How about a subreddit (or private subreddit)? reddit.com/r/esdiscuss <http://reddit.com/r/esdiscuss> is available.
Some prior art for high quality communities where language authors hang around: r/scala <http://reddit.com/r/scala/>, r/haskell <http://reddit.com/r/haskell/> (I’m sure there are more). > On Jul 25, 2017, at 10:31 PM, [email protected] wrote: > > Send es-discuss mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.mozilla.org/listinfo/es-discuss > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of es-discuss digest..." > Today's Topics: > > 1. Migrating to a better communication tool (Alexander Craggs) > 2. Re: Migrating to a better communication tool (kdex) > 3. Re: Return value of forEach (Naveen Chawla) > 4. Re: Migrating to a better communication tool (Claude Pache) > > From: "Alexander Craggs" <[email protected]> > Subject: Migrating to a better communication tool > Date: July 25, 2017 at 9:00:16 PM PDT > To: "" <[email protected]> > > > > Thought I'd move the topic of a new communication tool to it's own thread. > So that it doesn't pollute the (already polluted) removal of language > features thread. > > I took agree with Mark, I think it's time to move away from a mailing list > and the obvious choice for discussions like this is a forum. Discourse is > one option, but I'd also like to put our NodeBB[0] as another option. > > Thoughts of how it might be better than the current mailing list: > > - Doesn't pollute my inbox, option to subscribe and unsubscribe to > particular threads. > > - Stops replies from showing up on some mail clients > (https://puu.sh/wThmq/ae276dd806.png) > > - Universal formatting. esdiscuss.org seems to break formatting sometimes > (or put it in an attachement). > > Negatives: > > - People who already have a good system setup for mailing lists will have to > get used to working with a forum system. > > - Will require either a OAuth account (Github perhaps?) or an extra username > and password. > > [0] https://github.com/NodeBB/NodeBB > I hope more people read and search https://esdiscuss.org > <https://esdiscuss.org/>/ and engage with history instead of coming as if to > a blank slate. > > In all fairness, es-discuss is rather ancient in the way it works. I > personally would recommend es-discuss coming up with a better way to keep > track of its threads. The current setup is rather confusing, imo. FWIW, I > personally would recommend Discourse <https://www.discourse.org/>. I agree > with you on the same topics coming up constantly though. > > > > From: kdex <[email protected]> > Subject: Re: Migrating to a better communication tool > Date: July 25, 2017 at 9:26:09 PM PDT > To: [email protected] > > > I personally wouldn't mind using a forum instead. > > Another downside of this mailing list is that it doesn't really play nice > with > DKIM/DMARC, at least in my experience. > > On Wednesday, July 26, 2017 6:00:16 AM CEST Alexander Craggs wrote: >> Thought I'd move the topic of a new communication tool to it's own thread. >> So that it doesn't pollute the (already polluted) removal of language >> features thread. >> >> I took agree with Mark, I think it's time to move away from a mailing list >> and the obvious choice for discussions like this is a forum. Discourse is >> one option, but I'd also like to put our NodeBB[0] as another option. >> >> Thoughts of how it might be better than the current mailing list: >> >> - Doesn't pollute my inbox, option to subscribe and unsubscribe to >> particular threads. >> >> - Stops replies from showing up on some mail clients >> (https://puu.sh/wThmq/ae276dd806.png) >> >> - Universal formatting. esdiscuss.org seems to break formatting sometimes >> (or put it in an attachement). >> >> Negatives: >> >> - People who already have a good system setup for mailing lists will have >> to get used to working with a forum system. >> >> - Will require either a OAuth account (Github perhaps?) or an extra >> username and password. >> >> [0] https://github.com/NodeBB/NodeBB >> I hope more people read and search https://esdiscuss.org >> [https://esdiscuss.org/]/ and engage with history instead of coming as if >> to a blank slate. >> >> In all fairness, es-discuss is rather ancient in the way it works. I >> personally would recommend es-discuss coming up with a better way to keep >> track of its threads. The current setup is rather confusing, imo. FWIW, I >> personally would recommend Discourse [https://www.discourse.org/]. I agree >> with you on the same topics coming up constantly though. > > > > From: Naveen Chawla <[email protected]> > Subject: Re: Return value of forEach > Date: July 25, 2017 at 10:19:47 PM PDT > To: "T.J. Crowder" <[email protected]> > Cc: "[email protected]" <[email protected]> > > > On Tue, 25 Jul 2017 at 12:09 T.J. Crowder <[email protected] > <mailto:[email protected]>> wrote: > On Tue, Jul 25, 2017 at 5:06 AM, Naveen Chawla <[email protected] > <mailto:[email protected]>> wrote: > I would not overload `each` with any early termination, I would probably have > an `Array.prototype.takeWhile` method for that (which returns a new array > taking elements while the return value of the predicate is truthy). > > This is for when you don't want to create a new array, for either semantic or > memory pressure reasons. > > -- T.J. Crowder > > For that I would have `eachWhile` which returns the original array but only > iterates while the return value of the supplied callback is truthy. The > difference with `takeWhile` (which should be added to ES regardless, along > with `skipWhile`) is that in chaining calls `takeWhile` provides a > potentially smaller array for further processing, whereas `eachWhile` > doesn't. (`eachSkipWhile` could be the "skipWhile" counterpart to > `eachWhile`). > > I would leave `each` as a contract: always iterates through every value, > always returns the original array. > > For me this is better for readability. > > If these chained calls `map`, `each` etc. can be integrated with async > iterators (as RxJs attempts with Observables) then some really elegant stuff > can happen! > > > > From: Claude Pache <[email protected]> > Subject: Re: Migrating to a better communication tool > Date: July 25, 2017 at 10:31:24 PM PDT > To: Alexander Craggs <[email protected]> > Cc: [email protected] > > > Previous discussion: > > https://esdiscuss.org/topic/move-es-discuss-to-discuss-webplatform-org > <https://esdiscuss.org/topic/move-es-discuss-to-discuss-webplatform-org> > > —Claude > > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
