Crystal’s syntax is heavily inspired by Ruby’s, so it feels natural to read and easy to write, and has the added benefit of a lower learning curve for experienced Ruby devs.
Crystal is statically type checked, so any type errors will be caught early by the compiler rather than fail on runtime. Moreover, and to keep the language clean, Crystal has built-in type inference, so most type annotations are unneeded.
Null reference checks
All types are non-nilable in Crystal, and nilable variables are represented as a union between the type and nil. As a consequence, the compiler will automatically check for null references in compile time, helping prevent the dreadful billion-dollar mistake.
Running the previous file:
Crystal’s answer to metaprogramming is a powerful macro system, which ranges from basic templating and AST inspection, to types inspection and running arbitrary external programs.
Crystal uses green threads, called fibers, to achieve concurrency. Fibers communicate with each other using channels, as in Go or Clojure, without having to turn to shared memory or locks.
Crystal has a dedicated syntax to easily call native libraries, eliminating the need to reimplement low-level tasks.
Crystal libraries are packed as Shards, and distributed via Git without needing a centralised repository. Built in commands allow dependencies to be easily specified through a YAML file and fetched from their respective repositories.
Articles from our blog
Towards Crystal 1.0
The upcoming efforts to release Crystal 1.0
A platform for discovering the shards ecosystem.
|Crystal 0.35.1 released!||19 Jun 2020|
|Crystal 0.35.0 released!||09 Jun 2020|
|Crystal 0.34.0 released!||06 Apr 2020|
|Crystal 0.33.0 released!||14 Feb 2020|
|Crystal 0.32.1 released!||18 Dec 2019|
|Crystal 0.32.0 released!||11 Dec 2019|
|Crystal 0.31.1 released!||30 Sep 2019|
|Crystal 0.31.0 released!||23 Sep 2019|
|Crystal 0.30.1 released!||12 Aug 2019|
|Crystal 0.30.0 released!||01 Aug 2019|