5 ms·

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 num

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.

crooked-v 8y ago
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.
untog 8y ago
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.
pdelgallego 8y ago
I am looking forward to see some production ready versions of RY latest project Deno "A secure TypeScript runtime on V8" https://github.com/denoland/deno https://github.com/denoland/deno
- 52-6F-62 8y ago
  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?
  - steveklabnik 8y ago
    It was in Go, but in Ryan’s announcement, he said he was considering switching, and has since done so.
    - 52-6F-62 8y ago
      Cheers, Steve. I missed that.
  - justinsaccount 8y ago
    https://github.com/denoland/deno/commit/86354a29a40fb97e334f951428239ab8e171e2dd https://github.com/denoland/deno/commit/86354a29a40fb97e334f... https://github.com/denoland/deno/pull/276 https://github.com/denoland/deno/pull/276
    - 52-6F-62 8y ago
      Thanks guys. I'm out of the loop.