Indeed, not the appropriate mailing list.
(I can attest that I have been using object spread for almost a year. It is
mostly useful in a React and Redux setup, but probably not only. jQuery has
its shallow and not shallow extend method for a reason. I have been using
JavaScript extensively since around 2001, so not a novice by definition.)


☆*PhistucK*

On Sun, Apr 30, 2017 at 6:02 AM, kai zhu <[email protected]> wrote:

> i apologize if this is not the most appropriate mailing list, but i can’t
> help but express my frustration at the chaos in frontend-world caused by
> over-abuse of all the new es language features being introduced.  this
> rest/spread syntax is of particularly questionable use, and its likeliness
> to introduce bugs far outweighs its convenience, not to mention degrading
> overall code-readability and logic-reasoning for anyone besides the
> original coder.
>
> i sometimes wonder what the hell the tc39 committee members were thinking
> when they created the es6 language-spec.  are any of them *seriously*
> frontend-engineers?  do they realize almost none of es6 language features
> addresses practical frontend painpoints, and mostly exacerbates them,
> especially in the hands of novice javascript programmers (who are typically
> the only ones businesses outside of silicon-valley can afford to hire)?
>
> -kai
>
> On 28 Apr, 2017, at 0:10, PhistucK <[email protected]> wrote:
>
> Cool, thank you and sorry!
>
>
> ☆*PhistucK*
>
> On Thu, Apr 27, 2017 at 6:20 PM, Jeffrey Yasskin <[email protected]>
> wrote:
>
>> Stage 3 is exactly the stage at which implementations are supposed to
>> ship: https://tc39.github.io/process-document/, in particular the
>> entrance criteria for stage 4 require that 2 implementations have shipped.
>>
>> On Thu, Apr 27, 2017 at 2:06 AM, PhistucK <[email protected]> wrote:
>>
>>> Is it fine to ship it as it is a stage 3 proposal at the moment?
>>> See tc39/proposals <https://github.com/tc39/proposals>.
>>>
>>>
>>> ☆*PhistucK*
>>>
>>> On Fri, Apr 21, 2017 at 12:04 AM, Adam Klein <[email protected]> wrote:
>>>
>>>> Thanks, LGTM to ship!
>>>>
>>>> On Thu, Apr 20, 2017 at 12:38 PM, Sathya Gunasekaran <
>>>> [email protected]> wrote:
>>>>
>>>>> On Thu, Apr 20, 2017 at 12:31 PM, Adam Klein <[email protected]>
>>>>> wrote:
>>>>> > Are there test262 tests for this feature (do we pass them?)?
>>>>> >
>>>>>
>>>>> Yes. The tests were added here --
>>>>> https://github.com/tc39/test262/issues/865
>>>>>
>>>>> The latest test262 roll has pulled these tests into our harness --
>>>>> https://chromium-review.googlesource.com/c/471546/
>>>>>
>>>>> V8 passes all the tests.
>>>>>
>>>>> > On Thu, Apr 20, 2017 at 12:27 PM, Sathya Gunasekaran <
>>>>> [email protected]>
>>>>> > wrote:
>>>>> >>
>>>>> >> Contact Emails:
>>>>> >> [email protected]
>>>>> >>
>>>>> >> Spec:
>>>>> >> https://tc39.github.io/proposal-object-rest-spread/
>>>>> >>
>>>>> >> Summary:
>>>>> >> ECMAScript 6 introduced rest elements for array destructuring
>>>>> >> assignment and spread elements for array literals. This proposal
>>>>> >> introduces analogous rest properties for object destructuring
>>>>> >> assignment and spread properties for object literals.
>>>>> >>
>>>>> >> Rest properties collect the remaining own enumerable property keys
>>>>> >> that are not already picked off by the destructuring pattern. Those
>>>>> >> keys and their values are copied onto a new object.
>>>>> >>
>>>>> >> Spread properties in object initializers copies own enumerable
>>>>> >> properties from a provided object onto the newly created object.
>>>>> >>
>>>>> >> Interoperability and Compatibility Risk:
>>>>> >> This is a stage 3 feature.
>>>>> >>
>>>>> >> This new language feature allows syntax that was previously a
>>>>> >> SyntaxError, so compatibility risk is low.
>>>>> >>
>>>>> >> Webkit has shipped this in Safari Tech Preview Release 27. Firefox
>>>>> and
>>>>> >> Edge have not implemented this yet.
>>>>> >>
>>>>> >> Tracking bug:
>>>>> >> https://bugs.chromium.org/p/v8/issues/detail?id=5549
>>>>> >>
>>>>> >> Chrome status entry:
>>>>> >> https://www.chromestatus.com/feature/5657004848709632
>>>>> >>
>>>>> >>
>>>>> >
>>>>>
>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "blink-dev" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>>
>>>
>>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
>
>
>

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to