Re: Could we add the missing Regexp features from perl?

[Sebastian Zartner]

There are already a few regexp features in the pipeline, see
https://github.com/goyakin/es-regexp (listed in the Stage 0 proposals at
https://github.com/tc39/proposals/blob/master/stage-0-proposals.md).

The list of proposed features is not complete yet[1], though they already
cover some main itches ECMAScript's implementation is currently missing.

Sebastian

[1] Some missing features are listed at
http://www.regular-expressions.info/javascript.html

On 17 June 2016 at 18:19, Brian Jemilo II  wrote:

> Javascript regexp is based on a subset of perl's regexp engine, but its
> missing a lot of features that would make javascript more powerful.
> Wondering if we can put it into spec to add the missing features. Regexp is
> very powerful and currently, Javascript is being held by by the missing
> features.
>
> ___
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Re: Has there been any discussions around standardizing socket or file io usage?

[Bob Myers]

How does WebSockets fit into this?
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Re: ES7 - the standard

[Leo Balter]

There are some other changes, like the removal of Proxy trap and Reflect
method for enumerate, includes is also a new method for TypedArrays, as it
is different than Array#includes as it validates `this` as a valid
typedArray instance. ECMAScript code is now expressed using Unicode 8.0.0
or later (from 5.1 or later), etc.


One way to track this is searching for Normative changes on
github.com/tc39/ecma262 commits until Mar/2016.
While the commits are not perfectly flagged, it's another way to find some
other minor changes.

On Fri, Jun 17, 2016 at 3:50 AM, Thaddee Tyl  wrote:

> (Small typo, the path was changed to
> , since that is the
> direction we go for naming.)
> ___
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Could we add the missing Regexp features from perl?

[Brian Jemilo II]

Javascript regexp is based on a subset of perl's regexp engine, but its
missing a lot of features that would make javascript more powerful.
Wondering if we can put it into spec to add the missing features. Regexp is
very powerful and currently, Javascript is being held by by the missing
features.
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Re: Has there been any discussions around standardizing socket or file io usage?

[Boris Zbarsky]

On 6/17/16 10:35 AM, David Bruant wrote:

Specifically, even if there was a standard why would Node or browser
makers implement it given they already have an API for the job and lots
of code is already written on top of these APIs?


The other issue, of course, is that Node and browsers have very 
different security models, which has a significant impact on how a 
feature like this would be exposed.  The ideal API for one security 
model may not match the ideal API for the another one...


-Boris
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Re: Has there been any discussions around standardizing socket or file io usage?

[David Bruant]

Hi Kris,

Le 17/06/2016 06:44, Kris Siegel a écrit :
I didn't see this in the archives but I was curious if any 
consideration has been given for standardizing on features more 
commonly found in most other language's standard library.


For example reading and writing to sockets in JavaScript requires 
platform specific libraries and works very differently between them. 
The same goes for file io (which would obviously need restrictions 
when run in, say, a web browser).


Building these in would make JavaScript more universal and easier to 
learn (you learn one way to access a resource instead of 2 or 3 very 
different ways).


I would be happy to work on a proposal for such changes if they were 
desired by the community. Thoughts?
I understand your motivation, but I believe standardisation isn't the 
right avenue for the problem you describe to be solved.


Specifically, even if there was a standard why would Node or browser 
makers implement it given they already have an API for the job and lots 
of code is already written on top of these APIs?


Writing a standard is not a guarantee for implementation. Implementing 
something is lots of work for browser vendors and Node.js (and they're 
not in shortage of things to do), so they usually need some confidence 
that the new thing adds enough value to be worth the cost.
One way to convey such confidence can be to start the work, implement it 
as a library on top of current APIs, show that there is adoption by lots 
of people. Adoption is usually is an excellent proxy for value. That's 
how we got document.querySelectorAll (via jQuery) and Promise (via the 
gazillion promise libraries and Promise/A+ spec) for instance.


In this case, from experience reading proposals on standards 
mailing-list come and go, I doubt this will be of interest to enough 
people to be worth it. But that's just my own opinion and I would love 
to be proven wrong.


One more thing to regret, maybe https://www.youtube.com/watch?v=7eNFQqMSxtU

David
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Re: ES7 - the standard

[Thaddee Tyl]

(Small typo, the path was changed to
, since that is the
direction we go for naming.)
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Re: ES7 - the standard

[Thaddee Tyl]

> Could the spec next time have a non-normative section with the main
changes

I agree with Peter. For the purpose of being helpful, I tried making a
page related to the changes:
, so that it can be
linked to.

As far as I know, there is only Array.prototype.includes() and the
exponentiation operator added. Is there something else?
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Re: ES7 - the standard

[Peter van der Zee]

On Thu, Jun 16, 2016 at 11:54 PM, Raul-Sebastian Mihăilă
 wrote:
> I see that es7 is now a standard.
> http://www.ecma-international.org/ecma-262/7.0/index.html

Nice, thanks for the heads up.

Could the spec next time have a non-normative section with the main
changes compared to the previous? Something like section D and E but
without the compatibility reasons, just a quick overview of the new
features.

Can anyone point me in the direction of a resource that contains these
changes now?

- peter
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss