3 ms·
I actually dropped Ruby due to lack of typing, if Rails/Ruby gets static typing maybe people like me will come back. Another problem was lack of concurrency, I
by hfyasdflkjwa 2y ago
I actually dropped Ruby due to lack of typing, if Rails/Ruby gets static typing maybe people like me will come back.
Another problem was lack of concurrency, I don't know if that is still an issue today.
- diggan 2y ago> I actually dropped Ruby due to lack of typing, if Rails/Ruby gets static typing maybe people like me will come back. Not every language needs/should have static typing, so sounds like you just found a better language for your own needs, doesn't mean Ruby has to change. Personally I think it's perfect as it is :)
- berkes 2y agoSame here. But having worked with PHP and Python, who having typing annotations like Ruby can have through addons (sorbet) and might get to core someday, I would not go back to Ruby if it got this. Typing annotations in PHP or Python are hardly useful to me. Their net benefits aren't there for me. So, rather than trying to make Ruby (or Python, or PHP) like Rust, or .net or Java, why not just pick Rust, .net or Java instead? When I don't need typing, I'll gladly pick ruby still. But when I do, I don't want to shoehorn Ruby into something it was never designed to be, but instead pick an option that has typing designed into its core.