Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Richard
    @Naddiseo
    I think you get notifications..
    Luke Scott
    @lukescott
    I remember getting a digest from babel's gitter when they used it.
    Richard
    @Naddiseo
    yeah. do you know why they switched?
    Luke Scott
    @lukescott
    Slack is more friendly for large projects. It was good for me because the company I work for uses Slack for internal communication. So all I had to do was add babel as a team and I get notifications on my phone & computer.
    Gitter is good for stuff like this though.
    Richard
    @Naddiseo
    Yeah. It's simple and "just works"
    Okay.. where was that es-discuss thing
    Luke Scott
    @lukescott
    ?
    Richard
    @Naddiseo
    Couldn't remember the website
    let's have a look at some of the feedback
    Luke Scott
    @lukescott
    Oh. It's a mailing list. The es-discuss site just mirrors it. I had posted a message a while back. Didn't get too much - the discussion spiraled into class properties - although I think it was due to my TMI. I think we'll have to start a new topic on it.
    Richard
    @Naddiseo
    Yeah,
    I think for our proposal to get to stage 0/1, it needs to fairly minimal since type systems seems to be a bit of a land mine for the language architechs
    The major thing proposed is using the space separator.
    and I think the rationale we've come up with is a solid backing for that
    Now we just have to be able to convince the flowlang, and typescript people to change.
    but in order to do that, we're going to need to allow the two to be able to accomplish everything they can already do.
    Luke Scott
    @lukescott
    yeah. I think we're pretty close to that.
    Richard
    @Naddiseo
    (while keeping the changes to the es6/7 spec as minimal and non-polemique as possible)
    (can't remember the English word for polemique... (weird that English is my native language, and I can only think of the French word for the what I want to say))
    Luke Scott
    @lukescott
    The extra stuff that flow does - Like union types, type aliasing, declarations, etc... there's no reason whey they can't keep doing that. The can just do it without a :. They would just be "mostly standard".
    Richard
    @Naddiseo
    Yeah, I agree. I was thinking about that the other night.
    Luke Scott
    @lukescott
    polemique = controversial?
    Richard
    @Naddiseo
    It's possible we just specify how we have, then ts/flow can continue using what they have, but in the locations we've put forward. And I assume in the future another spec to expand TypeHint will arrive
    Yes! that's the word I wanted.
    and brendan eich has spoken on the binding isssue.
    Luke Scott
    @lukescott
    Yep. I'm not sure where they will land on it though. He is right, everyone prefers StrongScript classes. Wouldn't be in this mess if it was done that way in the first place.
    Richard
    @Naddiseo
    Yeah, I follow their reasoning. Bound by default would have been nice for classes
    The only reason I use them over prototype inheritance is it's less of a pain to type.
    Luke Scott
    @lukescott
    I was operating under the assumption it was far too late to change that.
    And I agree in principle. The issue is the cost. I'm not sure what the performance is of .bind. But implementations that pollyfill .bind cause 2x calls.
    Richard
    @Naddiseo
    bind is pretty expensive to call, and has a small (5-10%?) cost to call a bound function
    Luke Scott
    @lukescott
    This is an interesting benchmark http://jsperf.com/bind-vs-emulate/13
    emulated bind is actually faster by a huge margin.
    Richard
    @Naddiseo
    I think the native bind function has overhead to make it "spec-compliant"
    (Same with a fair number of native functions/classes)
    Richard
    @Naddiseo
    Did you read through the previous proposal made last september?
    Luke Scott
    @lukescott
    Was that the link you posted earlier or a new doc?
    Richard
    @Naddiseo
    I posted it in #17
    (second link)
    I looked through es-discuss for the last two years looking for type systems, those two were the only ones.
    Second link is an actual proposal similar to ours.
    Luke Scott
    @lukescott
    I didn't see it until now. I just read thru it. Seems to align with what we're trying to do. Just have to convince people to drop the : :).
    Richard
    @Naddiseo
    Yeah. Maybe we should contact the author of that spec, see if he's interested in bringing it up again.
    It looks like the resolution from that discussion is https://people.mozilla.org/~jorendorff/es6-draft.html#sec-forbidden-extensions
    The Syntactic Grammar must not be extended in any manner that allows the token : to immediate follow source text that matches the BindingIdentifier nonterminal symbol.
    That seems weird because of object destructuring..
    Luke Scott
    @lukescott
    This message was deleted
    Richard
    @Naddiseo
    I'm off to bed. I'll probably be online periodically during the day tomorrow while I'm taking breaks from work.
    Richard
    @Naddiseo
    @lukescott, I think we should shelve default types. And/or get some feedback from es-discuss on that specific issue.