Some grumpiness in quite a few comments. Pity.
This is an awfully nice language to work with, and the toolchain is starting to grow up - the compiler appears much speedier these days than it used to.
Also: A real grassroots effort unencumbered by megacorporation agendas (Yes, I know. Manas is a comparatively small Argentinian company, and kudos to them for having got the ball rolling). Give these guys a hand like they deserve.
If Crystal keeps on the way it promises, parallellism <i>will</i> be there, and will be a joy to handle.
Pro tip: when posting to HN, include a summary of "what it is"! It's often hard for readers to figure it out from a changelog.<p>From the docs:<p>"Crystal is a programming language with the following goals:<p>Have a syntax similar to Ruby (but compatibility with it is not a goal).<p>Be statically type-checked, but without having to specify the type of variables or method arguments.<p>Be able to call C code by writing bindings to it in Crystal.<p>Have compile-time evaluation and generation of code, to avoid boilerplate code.<p>Compile to efficient native code."<p>See: <a href="https://crystal-lang.org/docs/" rel="nofollow">https://crystal-lang.org/docs/</a>
No note of parallelism on the roadmap?<p><a href="https://github.com/crystal-lang/crystal/wiki/Roadmap" rel="nofollow">https://github.com/crystal-lang/crystal/wiki/Roadmap</a>
> In 0.25.0 we tried to improve the inferred type of unions of sibling types. Although it worked well for the compiler itself, some codebases out there exhibited some combinatorial explosion of unions due to this change.<p>What is a union of sibling types? Why would improving type inference require unions to be _generated_? I skimmed the PR referenced in the changelog, but it assumes domain knowledge I don't have (I'm only nominally familiar with Crystal).
People interested in Crystal might also be interested in <i>Inko</i>.<p>It's Ruby-ish but less compatible,
<a href="https://gitlab.com/inko-lang/inko" rel="nofollow">https://gitlab.com/inko-lang/inko</a><p>> <i>"Safe and concurrent object-oriented programming, without the headaches.
Inko is a gradually-typed, safe, object-oriented programming language for writing concurrent programs. By using lightweight isolated processes, data race conditions can not occur. The syntax is easy to learn and remember, and thanks to its error handling model you will never have to worry about unexpected runtime errors."</i>