TypeScript myths debunked

In my talk I want to present my take on popular myths about TypeScript and its ecosystem. I want to
talk about testing, frameworks, static types, TypeScript ecosystem. This won't be a rant to anybody -
I will give my arguments for or against common myths that are connected with TypeScript.

Transcript

1. TypeScript Myths
2. TypeScript Myths Debunked @krzysztof_zuraw
3. Who am I
4. Unit TESTS
5. It’s not needed when you have UNIT TESTS
6. It’s not needed when you have UNIT TESTS Busted
7. You don’t need tests anymore
8. You don’t need tests anymore Busted
9. Time Sink
10. Time Sink Busted
11. We ALREADY have unit tests
13. We ALREADY have unit tests Busted
14. It’s hard # to write ✍ unit tests
15. It’s hard # to write ✍ unit tests Busted
16. Frameworks
17. I don't want to build an application
18. I don't want to build an application Busted
19. + =
20. + = ❤
22. Static Types
23. Object composition Generic functions Polymorphism Higher order functions HARD
24. Syntax Noise
26. Syntax Noise At the beginning
27. guarantee program correctness Type correctness DOES NOT
28. guarantee program correctness Type correctness DOES NOT Busted
29. Barrier entry for library authors
30. Barrier entry for library authors Confirmed
31. E C O S Y S T E M
32. BECAUSE it is not JavaScript
33. + ,
34. External Libraries
35. External Libraries Busted
36. We were already BURNED by coffeescript ☕
37. TypeScript Roadmap
38. tinyurl.com/ TSRoadmap
39. We were already BURNED by coffeescript ☕ Busted
40. You CAN’T iteratively add it
41. You CAN’T iteratively add it Busted
42. Summary
43. Unit test - debunked Time sink - debunked Frameworks - no problem
44. Static Types - harder Syntax noise - debunked Barrier - confirmed
45. JavaScript - debunked Libraries - debunked Coffe - debunked
46. Thank you /