Message from JavaScript discussions
January 2018
— Type safe code is just not able to perform actions on an objects which would not work on the object
It literally could not do so because of the way the code would have to be designed, it's not run-time type checking
— Iterators are a great example of type safety in practice, because they standardize a data structure's serialization, meaning the code which prefers to rely on iterators is "more" type safe
— People at my workplace say that adding something i.e type safety to current workflow and adopting to that will slow it down
— And in a way it is thinking over something that i rather not have without considering type safety so there is some cost of time
— Now how much it would be and the will benifits outweigh the cost that i don't know yet
— Where is the time cost?
— Type safety in JS can be incrementally added
— So it's optional everywhere
— Additional step of thinking and adding type safety where its good to have but not needed
— Yeah that's true
— Which step?