Exciting news. Windows and multithreading are still showstoppers for me, unfortunately, but with the progress over the last couple years I'm hopeful that there's a light at the end of the tunnel on those fronts, especially now that the language itself is (ostensibly) stable.
Crystal 1.0 – What to expect
21–30 of 351 posts
Re: Crystal 1.0 – What to expect
#22Love the idea... could someone do a similar idea with Python.
Re: Crystal 1.0 – What to expect
#23Really happy to see this go 1.0. Between Crystal and Zig it's nice to see C++/Rust get some competition
Would a developer looking a Zig/C++/Rust really also consider Crystal? I figured Crystal was for Ruby developers who want a good static type system.
Crystal's appeal, for me at least, is the productivity of Ruby with the memory efficiency and execution speed of C++. Static typing is just a way of achieving that, it's not something I'm seeking per se.
Re: Crystal 1.0 – What to expect
#24Really happy to see this go 1.0. Between Crystal and Zig it's nice to see C++/Rust get some competition
Would a developer looking a Zig/C++/Rust really also consider Crystal? I figured Crystal was for Ruby developers who want a good static type system.
I mean, as someone who previously looked at Rust and is currently looking at Zig, Crystal is certainly on my radar.
That said, my current dayjob is around a Rails codebase, so I might not be representative of the normal systems programming crowd.
Re: Crystal 1.0 – What to expect
#25Really excited for Crystal.
We embarked on a huge project (search engine) using Crystal a year ago after also considering Rust. We have been very satisfied with the exceptional performance, language capabilities and the community.
Re: Crystal 1.0 – What to expect
#26I love the idea of Crystal but I remember reading that compilation times can balloon very quickly for moderately sized apps. Can anyone who writes Crystal today dispel or confirm that information? I imagine the inferred typing makes building a fast compiler really tough.
I just downloaded 1.0 and tried hello world. It took over 2 seconds. I hope that's just some kind of bug.
There is a cache that was previously cold. Subsequent runs should be faster. However compile times are longer than other languages like Go.
Re: Crystal 1.0 – What to expect
#27Congratulations
Re: Crystal 1.0 – What to expect
#28Huh - what's the last language that got mainstream adoption without backing from a large company? It almost seems impossible these days.
Ruby?
Re: Crystal 1.0 – What to expect
#29I love the idea of Crystal but I remember reading that compilation times can balloon very quickly for moderately sized apps. Can anyone who writes Crystal today dispel or confirm that information? I imagine the inferred typing makes building a fast compiler really tough.
Was that possibly before they backed off from global type inference? I think that was the cause of long compilation times. They require you to annotate a few types manually now which is an effective cut.
They haven’t backed off from global inference. They did move to require you to type collections, but methods are not inferred at definition but rather at invocation and it happens globally.
There is no solution really. If you want a language to feel like it is dynamically typed but actually has types, something gotta give, and in this case it is compilation times. And it gets quite high fast.
Re: Crystal 1.0 – What to expect
#30How does it compare to Nim?
Nim is more mature and a with a lot bigger community with diffrent focus.
Crystal focus is pure web trying to be Ruby and Nim is more like python.