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)
Subject: Migrating to a better communication tool
Date: July 25, 2017 at 9:00:16 PM PDT
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/ 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. I agree with you on the same topics coming up constantly though.
Subject: Re: Migrating to a better communication tool
Date: July 25, 2017 at 9:26:09 PM PDT
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.
Subject: Re: Return value of forEach
Date: July 25, 2017 at 10:19:47 PM PDT
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!
Subject: Re: Migrating to a better communication tool
Date: July 25, 2017 at 10:31:24 PM PDT
Previous discussion:
—Claude
_______________________________________________
es-discuss mailing list
[email protected]https://mail.mozilla.org/listinfo/es-discuss
