2 ms·
I’ve taken several clients projects from conception to production with crystal lang. It’s more production ready than much I’ve encountered elsewhere with less
by iostream24 4y ago
I’ve taken several clients projects from conception to production with crystal lang.
It’s more production ready than much I’ve encountered elsewhere with less need for external “shards” or libraries.
The executables are small and to give you one example: a nodejs app that used 500mb of ram is now consuming 25mb as a crystal executable that doesn’t require any minding and happily runs for months with no change in the overall memory consumption or evident leakage. This executable was built on the same machine it runs on and can use normal systemd units and controls etc.
The standard library is built for purpose and has most of what you need.
I agree that compile times are slower than ideal but not like c++ slow or anything, like 30 seconds for one app that’s roughly 30k LOC fwiw.
I use a combo of standard lib .ecr server rendered templates and named js bundles from the frontend build toolchain to speed up the dev cycle. Most backend functionality in crystal works as intended once it compiles.
I really wouldn’t consider anything but Rust an improvement (gets rid of our Boehm GC) as crystal is just nicer to work with than Go, and less hassle or nonsense than c or c++…
Obviously it blows the doors off anyway interpreted even with native extensions… it is FAST