When comparing Flow vs Imba, the Slant community recommends Imba for most people. In the question“What are the best solutions to "The JavaScript Problem"?” Imba is ranked 28th while Flow is ranked 32nd. The most important reason people chose Imba is:
The ‘imperative’ DOM from Imba is factors of magnitudes faster than most current virtual DOMs.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Checks to see if you check for Nulls
Because getting those exceptions is just not fun and very pervasive.
Pro Versioned type definitions
Pro There is support in many code editors via the extension
For example, there is good support through the extension in Visual Studio Code, which is a good editor for TypeScript, which is a competitor to Flow.
Pro Babel extension for strip of type annotations
Thanks to the Babel extension for the output, there is minimally modified code that is understandable to the author.
Pro Statical analysing of JavaScript code
Statical analysing of JavaScript code without pre-making any changes to it. But supported annotation types by extending the syntax of the language.
Pro Super super fast DOM implementation
The ‘imperative’ DOM from Imba is factors of magnitudes faster than most current virtual DOMs.
Pro Transpiles to very readable Javascript
Pro React inspired approach
Pro Close alignment between language and DOM
The DOM is a first class citizen of Imba and that allows for short elegant interaction.
Pro Ruby inspired syntax
Cons
Con Weak base type definitions even for popular JavaScript libraries
For example, there are definitions for Gulp, React.
Con Still a young language
But looks very promising.