tc39-notes

It’s about strictness scoping. https://old.reddit.com/r/webdev/comments/v877zq/why_cant_you... gives a decent explanation, and https://github.com/rwaldron/tc39-notes/blob/d0c651b358b361b0... is good and technical.

I actually didn’t look hard enough: there is a proposal[0] for something that could be called ‘BigDecimal’ in ECMAScript, but it’s a stage 0 proposal[1]. As for why a decimal type hasn’t progressed further in ECMAScript you’ll want to read the notes [2] from the meeting where the latest proposal was discussed. [0] https://docs.google.com/presentation/d/1jPsw7EGsS6BW59_BDRu9... [1] https://github.com/tc39/proposals/blob/master/stage-0-propos... [2] https://github.com/rwaldron/tc39-notes/blob/b8da60318b564f13...

v8 did and then pulled support. JSC (javascript core) added support in June/July 2016 (a year and a half ago). Their team makes some great points about this. https://github.com/tc39/ecma262/issues/535 https://github.com/rwaldron/tc39-notes/blob/master/es7/2016-... For all of Google's talk about their syntactic tail call proposal, they haven't cared enough to implement it -- only to remove their PTC code. FF and MS are in the same position. At this point, I don't really care one way or the other, they need to quit the excuses, quit the petty power struggles, and do something one way or the other. Every year they wait is another year before we can use it. EDIT: I'd also add that the performance impact in the real world seems to be close to zero. https://github.com/tc39/proposal-ptc-syntax/issues/7

For the record, many implementors are against STC and PTC for a few reasons: - It may be significantly slower than regular recursive calls (though this claim seems to be false both in practice and theory) - It may break debug tools - It may break browser telemetry (especially on IE) Additionally, they would have to decide on an explicit syntax for STC (return.tail or something like that). Personally, I would love to see STC anf PTC land so I can write proper functional code in JS. It would also make functional programming in JS easier to teach (less gotchas). See TC39 discussion: https://github.com/rwaldron/tc39-notes/blob/master/es7/2016-...

> It would be nice to be able to read some of the discussion of the standardization process and see how these performance trade-offs where considered. Anyone has some pointers? There's the mailing list at https://esdiscuss.org/ More recently there's been more discussion around specific proposals in github repos under the tc39 org: https://github.com/tc39 And Rick Waldron takes TC39 meeting notes in this repo: https://github.com/rwaldron/tc39-notes

OP missed some more development on recent gradual typing efforts in dynamic languages. I collected those links below when implementing gradual typing for perl5. perl5 is more lucky than ruby, since perl5 supports syntax for types in lexical variable declarations for decades already, and more via attributes. http://www.typescriptlang.org/Content/TypeScript%20Language%... (microsoft's javascript with types) https://code.facebook.com/posts/1505962329687926/flow-a-new-... (facebook's javascript with types) https://github.com/rwaldron/tc39-notes/blob/master/es6/2015-... Soundscript, google's javascript with types https://www.python.org/dev/peps/pep-0484/ (planned python with types) http://www.mypy-lang.org/ (existing python with types) https://news.ycombinator.com/item?id=8620129 (ruby 3.0 planned with types) http://crystal-lang.org/ (a good

The target date for ES6 has slipped to December 2014: https://github.com/rwaldron/tc39-notes/blob/48c5d285bf8bf0c4...

- November 2013, Final review draft - June 2014, Editorially complete (STH: we said June in the meeting, but July makes more sense, since we don't have to submit to the GA until September, IIUC) - December 2014, ECMA approval https://github.com/rwaldron/tc39-notes/blob/48c5d285bf8bf0c4...