Re:TypeScript at Google
by kylecordes on Saturday September 01, 2018 @10:25PM
(#17895169)
I'm really eager to see availability of some extra features via this new pathway.
But I am less excited about projects containing TypeScript plus the large number of transitive dependencies from a typical Babel set up; I've been greatly enjoying TypeScript instead of that.
Re:TypeScript at Google
by pdelgallego on Sunday September 02, 2018 @08:34AM
(#17896762)
I am looking forward to see some production ready versions of RY latest project Deno "A secure TypeScript runtime on V8"
Written in Go rather than C++ no less.
Edit: wait it looks like they’ve changed to all Rust with C++ for the libraries. I haven’t looked at the codebase since the spring. Am I crazy that i could have sworn it was written in Go previously?
Re:TypeScript at Google
by justinsaccount on Sunday September 02, 2018 @03:00PM
(#17898110)
Thanks guys. I'm out of the loop.
Re:TypeScript at Google
by steveklabnik on Sunday September 02, 2018 @01:57PM
(#17897872)
It was in Go, but in Ryan’s announcement, he said he was considering switching, and has since done so.
Cheers, Steve. I missed that.
100% agreed. It was incredibly liberating to move from Babel with its byzantine level of configuration and plugins to "just run tsc". So much easier to reckon with - Typescript is Typescript is Typescript.
For my part, my web projects have generally ended up with both Typescript and Babel because of old-browser-support reasons, so integrated parsing simplifies things for me.
Until this showstopper is fixed (it's been almost 9 months now), some of us can't move forward with Babel 7: https://github.com/babel/babel/issues/7074
https://blogs.msdn.microsoft.com/typescript/2018/08/27/types...