Re:Convert React JavaScript Code to TypeScript with Proper T...
by O4epegb on Wednesday January 17, 2018 @01:47AM
(#16165983)
Strict null in TS was before flow public release.
Re:Convert React JavaScript Code to TypeScript with Proper T...
by gr__or on Wednesday January 17, 2018 @06:04AM
(#16166990)
That is not true at all!
Flow was announced November 18, 2014: https://code.facebook.com/posts/1505962329687926/flow-a-new-...
Typescript got --strictNullChecks with Version 2 which was announced July 11, 2016: https://blogs.msdn.microsoft.com/typescript/2016/07/11/annou...
Even if I'm being charitable and look for the date when the PR (https://github.com/Microsoft/TypeScript/pull/7140) was merged, we'd only get April 2016.
Them being separate allows the projects to try stuff the other group disagrees with and prove they are right. I very much like that.
Beyond that, the 2 projects really are VERY different. Again, with strict null and all the pain, it's causing on the TS side. It's not easy to just bring in features of one and merge them to the other. The entire architecture is different (eg: the flow inference). Then there's the pitty shit: I don't know if they're involved with TS, but some very visible Facebook people just can't handle the fact that the entire world doesn't revolve around Unix, as nice as it would be if it did.
Some stuff is sparking some collaboration. Babel getting support for TypeScript syntax for example.