> So, what’s the catch?
No windows support. (Seems to be progressing, though)
No windows support. (Seems to be progressing, though)
But for many applications that's a non-issue.
Yet the Crystal team hasn't made a preview windows build which can enable all those use cases and the act of using Crystal on Windows is super convoluted as a result.
There is some caching to help but times are still high. IIRC the compiler is not parallel either, so having more cores won't help.
There is also a —release compile flag that you would want to use for production and it is much slower.
I think they stepped back from this a few years ago. It's not globally inferred anymore - you need to specify some types manually.