News for hackers. Stuff that matters.
Re:The cost of transpiling ES2015 in 2016 by MrPatan on Monday February 08, 2016 @10:05AM (#11058441)
Transpiling will go away when people stop trying to push their own web-breaking language.

It wasn't cool for Microsoft to push JScript in the 90s, why is it cool now for it to push TypeScript? And allied with Google, no less!

Re:The cost of transpiling ES2015 in 2016 by spion on Monday February 08, 2016 @10:17AM (#11058524)
Because:

1. JScript added conditional compilation directly in the browser which was IE-only (extend, extinguish). TypeScript compiles to cross-browser JavaScript (which does none of the above)

2. TC39 is supposed to be working in a "pave the cowpaths" (1) mode. Before new features get integrated into EcmaScript, TC39 looks into what the community is already doing (existing cowpaths), then integrates that into the language. Not only that but TC39 can learn from the mistakes of TS and Flowtype when they add type system support in EcmaScript. We are in dire need of one - and thanks to Microsoft's and Facebook's explorations, we now know what kind of type system would work for JS.

(1) For example, we got arrow functions in ES2015 thanks to CoffeeScript.

Re:The cost of transpiling ES2015 in 2016 by kristiandupont on Monday February 08, 2016 @10:20AM (#11058538)
Why is that not cool? It's not like they are forcing anyone to anything (like you could argue was the case in the 90's).

I don't use it but I appreciate that the JS is being explored and expanded by projects like it and many others.

Re:The cost of transpiling ES2015 in 2016 by izym on Monday February 08, 2016 @02:04PM (#11060149)
Because JScript was an MS-only implementation, while TS always has and always will compile to JS. There's quite a difference.

Also, could you elaborate "web breaking" w.r.t. compile-to-JS languages?