why i was wrong about typescript
play

Why I Was Wrong About TypeScript TJ VanToll TypeScript TypeScript - PowerPoint PPT Presentation

Why I Was Wrong About TypeScript TJ VanToll TypeScript TypeScript TypeScript Why I Was Wrong About TypeScript Whether TypeScript is a good fit for your next project Why I Was Wrong About TypeScript A typed superset of JavaScript


  1. Why I Was Wrong About TypeScript TJ VanToll

  2. TypeScript

  3. TypeScript

  4. TypeScript

  5. Why I Was Wrong About TypeScript

  6. Whether TypeScript is a good fit for your next project

  7. Why I Was Wrong About TypeScript

  8. “A typed superset of JavaScript that compiles to plain JavaScript”

  9. “A typed superset of JavaScript that compiles to plain JavaScript ”

  10. 😎

  11. 😡

  12. Compile to JavaScript tools • There are a lot. • 345 • Source: https://github.com/jashkenas/coffeescript/wiki/List-of- languages-that-compile-to-JS • Ruby, Python, Erlang, Java, Scala, C#, F#, Lisp, Scheme, Haskell, Smalltalk, C, C++, Basic, Go, PHP , and way more.

  13. Fun names of compile-to-JS tools • treehugger • jangaroo • Waterbear

  14. http://waterbearlang.com/

  15. Compile to JavaScript tools • There are a lot. • 345 • Source: https://github.com/jashkenas/coffeescript/wiki/List-of- languages-that-compile-to-JS • Ruby, Python, Erlang, Java, Scala, C#, F#, Lisp, Scheme, Haskell, Smalltalk, C, C++, Basic, Go, PHP , and way more.

  16. Why I Was Wrong About TypeScript

  17. “We risk a lot by building our core on top of TypeScript.”

  18. “I don’t hear anyone talking about TypeScript.”

  19. “I like to keep my JavaScript pure, as God intended.”

  20. Why I Was Wrong About TypeScript

  21. Why?

  22. 3 reasons

  23. 1) Commitment to the ECMAScript standard

  24. “Some examples [of compile-to-JavaScript frameworks], like Dart, portend that JavaScript has fundamental flaws and to support these scenarios requires a “clean break” from JavaScript in both syntax and runtime. We disagree with this point of view. We believe that with committee participant focus, the standards runtime can be expanded and the syntactic features necessary to support JavaScript at scale can be built upon the existing JavaScript standard .”

  25. 2) Types are opt-in

  26. 3) Tooling

  27. So should you use TypeScript? • Are your apps big? • Do you work on a team? • Unfamiliar codebases? • Non JS developers that need to write JS code?

  28. http://developerday.nativescript.org/?dis count=TJVANTOLL

  29. Thanks! @tjvantoll

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend