Skip to content

Instantly share code, notes, and snippets.

@tkachenko1503

tkachenko1503/why-do-we-need-types-in-javascript.md

Last active April 21, 2020 10:35
Show Gist options
  • Star 74 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tkachenko1503/b32d1a7a70b444720cd8c4ac4e57565d to your computer and use it in GitHub Desktop.
Save tkachenko1503/b32d1a7a70b444720cd8c4ac4e57565d to your computer and use it in GitHub Desktop.
Download ZIP
Do we need types in JavaScript? Or maybe not?
Raw
why-do-we-need-types-in-javascript.md

This is my lightning talk submission to ReactiveConf 2018 https://reactiveconf.com/

In this talk, I want to share my experience gained during the development of frontend applications in several programming languages.

I think it's not a secret for anybody that developing large JavaScript applications is not so easy as it seems at first glance. We all want something simpler and more reliable. Therefore, many developers and even entire companies switch to different, compiled in JavaScript, programming languages. The bulk of such transitions is accounted for TypeScript and flow, and often, developers faced with more problems than they were before.

I wasn't the exception. Moving to a new project, I started using TypeScript and was disappointed. Luckily in my next project I used ClojureScript and it was like everything is illuminated!

Since then, I know exactly what the recipe for simple and reliable code (even in plain old JavaScript). And I want to share this recipe with you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment