The trade off for that powerful type inference is a slow compiler.
And it's 20 times faster than MRI Ruby JIT 3.0, see http://software.rochus-keller.ch/are-we-fast-yet_crystal_rub.... It's a pity Ruby typing went in another direction.
> The trade off for that powerful type inference is a slow compiler.
When run in the default (i.e. no release, debug) mode, build time is ok, especially for rebuilds when only one file has changed which is less than a second. Release builds are slow (see my PDF).
And how are the justifications appalling? He thinks annotations are a detriment to the expressiveness of the language, and Ruby prides itself on being expressive.
As for being a reduction to the expressiveness of the language, I think Haskell is proof that you can have annotations without reducing the expressiveness of the language. Type annotations in Haskell and Idris don’t even interfere with value-level syntax!
At 12:20 minute mark he basically says he doesn't like annotations, and calls the separate file a compromise several times. At 19:46, he admits it's hard to maintain separate files. At 20:57 he says annotations are not DRY, would change the language, and aren't necessary for performance (points to V8/Chrome). At 23:10 he says no to annotations because he thinks one day the tools will be smart enough to give you the same guarantees/diagnostics without them, so at 24:50 he concludes that he doesn't want to have to remove annotations when that comes to pass.
(don't shoot the messenger! I don't necessarily agree with these conclusions...)
(edit: tried to make the summary clearer)