News for hackers. Stuff that matters.
Re:Facebook Launches Flow, Static Type Checker for JavaScript by Touche on Tuesday November 18, 2014 @06:29PM (#8627090)
I'm not sure if what you are describing is that realistic. A function that is used in some weird incorrect way that it won't get caught in development, QA or unit testing? Perhaps that can happen, but it's not been my experience. I use assertions liberally; they are especially helpful when refactoring and trying to figure out all of the dependent code that needs to be updated.

Sure it's less certain than what you get from a compiler; that's the tradeoff for not having to compile in development. Since most JavaScript code is not type-sensitive it's only important in code that you are more than likely going to be testing heavily anyways.

Re:Facebook Launches Flow, Static Type Checker for JavaScript by arjie on Tuesday November 18, 2014 @10:05PM (#8627990)
The point is that you substitute the extra testing and QA with types. The assertion doesn't guarantee type correctness, so you test that function and downstream functions. That's extra code burden. Instead, you could have type checking.
Re:Facebook Launches Flow, Static Type Checker for JavaScript by Touche on Wednesday November 19, 2014 @09:09AM (#8630052)
I disagree, tests and QA happens regardless. Adding a compile step to development is a big downside to the type approach.