First I was excited about optional typing in Ruby, but now that I see that they've split the type signature into separate .rbs files I'm rather sceptic. I've also taken a look at sorbet and their ruby syntax, but don't like it either. I guess the whole topic is just much more complex than I thought. Anyway, I'm currently installing steep and the VS Code extension to see if it helps me.
I guess Ractor is less controversial and most ruby developers appreciate this kind of parallelism with multiple GVL's/RVM's.
Passionate about everything related to computer science. Working as devops engineer and studying ML and blockchain. Currently working on https://github.com/Noovolari/leapp
Passionate about everything related to computer science. Working as devops engineer and studying ML and blockchain. Currently working on https://github.com/Noovolari/leapp
I'll start by saying that I don't really like the design choice of RBS. I tried it and feels a bit cumbersome having to go back and forth from one file to another to define it's behavior.
We're a place where coders share, stay up-to-date and grow their careers.
Top comments (3)
First I was excited about optional typing in Ruby, but now that I see that they've split the type signature into separate
.rbsfiles I'm rather sceptic. I've also taken a look at sorbet and their ruby syntax, but don't like it either. I guess the whole topic is just much more complex than I thought. Anyway, I'm currently installing steep and the VS Code extension to see if it helps me.I guess Ractor is less controversial and most ruby developers appreciate this kind of parallelism with multiple GVL's/RVM's.
My thoughts exactly
I'll start by saying that I don't really like the design choice of RBS. I tried it and feels a bit cumbersome having to go back and forth from one file to another to define it's behavior.