Submitted by Souvik Basu (@souvikbasu) on Thursday, 25 January 2018
Most JS frameworks and libraries today are opting for type safety to handle application complexity for large codebases. But is it really needed? Does that slow down development efforts and runtime performance? Or is it actually a good move?
- JS as it was designed pre 2014
- advent of TypeScript, Flow, PropTypes
- When is type safety needed? When it is not?
- Implication of type safety on JS code maintainability and writability
- Implications on runtime performance
Souvik is a JS enthusiasts with 15 years experience in the industry. His day job is to set up a team on React project in Tesco Bengaluru. He loves to code equally well in React as well as in Angular. Currently he is spending a lot of time exploring Conversational UI.