Re: Re: JavaScript Versioning

2017-07-23 Thread David White
Sorry, just seen this thread and thought it worth mentioning a similar thread ongoing here that has derived from wanting to remove less popular features from the specification: https://esdiscuss.org/topic/removal-of-language-features We should definitely continue this conversation in this threa

Re: Removal of language features

2017-07-23 Thread David White
ot;application/javascript.2" ? > > -----Original Message- > From: David White [mailto:david.rhys.wh...@icloud.com] > Sent: Sunday, July 23, 2017 7:35 PM > To: doodad-js Admin > Subject: Re: Removal of language features > > That’s an interesting proposal but I’m strug

Re: Removal of language features

2017-07-23 Thread David White
runtime in order to allow the language to progress more natrurally? > On 23 Jul 2017, at 23:38, doodad-js Admin wrote: > > Maybe that's time to start a new major version of JS? > > -Original Message- > From: David White [mailto:david.rhys.wh...@icloud.com] > Sen

Re: Re: Removal of language features

2017-07-23 Thread David White
Lots of good thoughts and discussions here, and while it’s gone slightly off topic I’d love to discuss the possibilities of how we could get JavaScript to a point where we could actively remove features with every new specification. I’m sure nobody would want to break the web, which would be ver

Removal of language features

2017-07-19 Thread David White
Hi, I’m just curious as there are a lot of proposals for the addition of features to the ES specification, is there any scope for requests to remove language features? Going via the same means of writing a proposition that would attempt to support the removal of a feature, ultimately simplifyi

Re: es-discuss Digest, Vol 125, Issue 51

2017-07-16 Thread David White
Too many operators can become quite confusing, having worked with many functional languages I find the number of operators more of a hinder than help. I’m very pro functional operators when they help me read the code explicitly rather than implicitly, for example with the `|>` pipeline operator,

Re: Pipe operator for JavaScript

2017-07-11 Thread David White
issues/33#issuecomment-306986211 > > <https://github.com/gilbert/es-pipeline-operator/issues/33#issuecomment-306986211> > > On Tue, Jul 11, 2017 at 1:02 PM, David White <mailto:david.rhys.wh...@icloud.com>> wrote: > Piping is useful when composing many small pure functions to

Pipe operator for JavaScript

2017-07-11 Thread David White
Piping is useful when composing many small pure functions together, one problem with this is the evaluation needs to be read from the inner most expression value in reverse to the outer most function call. Given the following statement we can see that it would be read as 'call math round then ca