3 ms·
You replied downstream of me, but: being non-Ruby in terms of semantics is a pretty big minus for me, to be honest. If it looks like Ruby, I expect it to act li
by eropple 10y ago
You replied downstream of me, but: being non-Ruby in terms of semantics is a pretty big minus for me, to be honest. If it looks like Ruby, I expect it to act like Ruby and the cognitive load of dealing with such similar syntax without having similar semantics is more than I want to deal with without getting a big win. And Crystal is not a big win to me; my choices aren't Java or C, my choices are Kotlin-or-Scala, C#, and C++ rather than C. And the next step for me would be Rust, which I think does a good job of taking lessons from Ruby rather than imitating it.
It's not a bad language. (I would rather see it than Go in just about any situation.) But I don't see a positive value prop, for me, as I don't particularly value syntax (I can write anything; even if syntax was a big pain point for me, this is why I use IntelliJ and ReSharper/ReSharper C++) and I do value ecosystem and tooling. Maybe if it was JVM-targeted or CLR-targeted, to piggyback off those ecosystems, but even then the value prop is muddy.