This is a pretty interesting read. It looks like there are some exciting things happening in Ruby. I am new to Ruby, but I have been learning it after years of python and Java and Javascript, since I took a job at a Ruby shop. And I am falling in love with it. Its a really nice language, and I prefer ruby to Python personally. I like that Ruby has a small talk like sense of sending messages.
Where is Ruby Headed in 2021?
31–40 of 360 posts
Re: Where is Ruby Headed in 2021?
#32I know I'm going to take it on this chin for this but if I'm gonna be honest I hope "away, forever."
Re: Where is Ruby Headed in 2021?
#33We are hiring the type of rails developer reading this thread.
BackNine Insurance (quoteandapply.io) | Remote | Rails Developer We automate life insurance from submission to commission so companies can easily sell online. Thousands of companies (from brick and mortar insurance agencies to publicly traded banks) use BackNine's software to quote, apply, and manage their life insurance business online.
We need a Rails developer with 2+ years of professional experience.
Please email reid@back9ins.com
Re: Where is Ruby Headed in 2021?
#34Honestly I don't get why some people want to move to static types. Ruby is a dynamic language, that's the point of it... Giant orgs can just use Java or something. We need some languages to stay productive for those of us who work solo or in small groups. If I wanted static types I'd use Java, Go or something (probably Haskell).
Ruby isn't forcing you to use static types. That being said, I actually think something like Sorbet makes even solo/small teams more productive because it trades some additional time writing boilerplate for dramatically reducing the number of bugs you write.
A good test suite is better at keeping the code bug free.
Not needing types is another benefit of good testing.
That's my experience, at least.
Re: Where is Ruby Headed in 2021?
#35Honestly I don't get why some people want to move to static types. Ruby is a dynamic language, that's the point of it... Giant orgs can just use Java or something. We need some languages to stay productive for those of us who work solo or in small groups. If I wanted static types I'd use Java, Go or something (probably Haskell).
I really feel the same about javascript with typescript. It feels a heck of a lot like new grads or old c#/java devs trying to keep up with the times by switching to javascript, but then resisting the code structure and loose typings.
It's interesting though how much more robust the library ecosystem has become after Typescript attracted a new crowd that wouldn't haven otherwise gone near JavaScript with a ten foot pole..
Maybe with the new developments in Ruby ecosystem somebody will fix Net::Http so an absolute request timeout can be set to protect against slow client/server and maybe oversized payloads as well. Maybe 2030?
Re: Where is Ruby Headed in 2021?
#36Earlier quoted context omitted.
I tend to use guard statements in ruby methods to prevent invalid input. It helps people understand how the method is supposed to be used while also failing early with an obvious error, rather than late with a cryptic one. If there was a way to do a type signatures inline without making things ugly, I would use them. Optionally enforcing @param and @return comments would be good enough for me. A separate file is usel…
You might not use "an IDE", but you can get language server support for a ton of languages in almost any text editor worth using these days. There are Vim LSP plugins for TypeScript, even.
I suppose. I use a number of linters with Sublime.(1) It’s just not as rich or integrated as a real IDE would be.
1: I have my reasons for using Sublime over the alternatives.
Re: Where is Ruby Headed in 2021?
#37The future of Ruby is in Crystal
Re: Where is Ruby Headed in 2021?
#38This is really cool. I’ve used a number of languages and dabbled in a few frameworks but nothing I’ve used brings me joy like ruby does. I approach programming creatively. I think in large systems and architecture. Ruby allows me to skip worrying about the details. Code blocks abstract away thinking about loops and just focus on data. Just about every array operation I could want is there, waiting for a code block. I…
I just left a rails gig to go back to django. I like ruby ok but not a big fan of rails.
I totally see the value and understand why someone would like it but I just never could get to that point with it.
I much prefer the explicit imports, loops, etc I suppose
Re: Where is Ruby Headed in 2021?
#39Earlier quoted context omitted.
Ruby isn't forcing you to use static types. That being said, I actually think something like Sorbet makes even solo/small teams more productive because it trades some additional time writing boilerplate for dramatically reducing the number of bugs you write.
A good test suite is better at keeping the code bug free. Not needing types is another benefit of good testing. That's my experience, at least.
Do you think it's possible for well used types to displace the need for some tests?
Re: Where is Ruby Headed in 2021?
#40Honestly I don't get why some people want to move to static types. Ruby is a dynamic language, that's the point of it... Giant orgs can just use Java or something. We need some languages to stay productive for those of us who work solo or in small groups. If I wanted static types I'd use Java, Go or something (probably Haskell).
Ruby isn't forcing you to use static types. That being said, I actually think something like Sorbet makes even solo/small teams more productive because it trades some additional time writing boilerplate for dramatically reducing the number of bugs you write.
dramatically reducing the number of bugs you write.
I would say that's a big overstatement.