If you like or want more static typing in , what do you consider the strongest arguments in favor of it:

* Better editor tooling
* Pre-execution code validation
* Runtime data validation
* Possible performance improvements

Something else?

7
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Greg Donald

@noelrap 'crystal' is just way too hard to spell ๐Ÿ˜‚

0
5mo
LyallMorrison

@noelrap make ruby developers decide what the return type of their functions is ๐Ÿ˜ 

0
5mo
Bradley Schaefer

@noelrap longer dev cycles, making developers more money for doing the same work

1
5mo
Sami Samhuri

@noelrap Editor tooling for me, with performance a distant second.

Pre-execution validation is nice but I actually also kind of like that the absence of that guarantee means you really have to have good test coverage to avoid silly runtime errors.

0
5mo
PointlessOne

@noelrap API documentation.

0
5mo
scottyp

@noelrap For me it's about tightening up the feedback loop.

I want the type checker to tell me that assumptions I've made are wrong and that, for example, the method I've been testing with a symbol parameter is going to be passed a string from the API layer. It sucks to only find that one out in production when the alerts start going off.

Stupid mistakes like that should be surfaced as soon as I've finished typing the method call/signature.

1
5mo
Damax

@noelrap writing less tests. Writing only business logic tests.

0
5mo
Replies