I think the one thing that will always keep Ruby around is how easy it is to start off with when you're first learning to code. The readability of it, its elegance, the Ruby community -- these things lower the barrier of entry when it comes to being able to pick up a language, its associated framework, and the different contexts in which it ends up being the right tool for the job. It makes it really easy to hit the ground running and start being productive, particularly if you're still fairly new to the field.
Ultimately, though, I see Ruby + Rails being used more and more as an API layer. While the JavaScript wars mean that front end frameworks are in flux all the time, Ruby feels like a far more stable choice for architecting an API that people will be able to work on and contribute to easily. I'll be interested to see how Ruby adapts and changes to high-performing (read: much faster) languages, like Rust. Personally, I'm keeping my eye on things like Helix, which makes the future of Ruby seem super bright.
Helix looks way further along than when I last heard about it. That is absolutely going to be a big boon for Ruby.
I asked this question because I have a hard time articulating why I stick with Ruby. DHH's keynote which touched on culture said a lot, but I still am not sure. A couple months ago I wrote a classic Ruby bug where I passed the wrong value to a method and it really made me yearn for some stronger typing.
In many ways Ruby fits my personality and I get what DHH often says about the community and culture, but I often feel at odds with it, like intellectually.
Thanks for a really well-articulated view.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think the one thing that will always keep Ruby around is how easy it is to start off with when you're first learning to code. The readability of it, its elegance, the Ruby community -- these things lower the barrier of entry when it comes to being able to pick up a language, its associated framework, and the different contexts in which it ends up being the right tool for the job. It makes it really easy to hit the ground running and start being productive, particularly if you're still fairly new to the field.
Ultimately, though, I see Ruby + Rails being used more and more as an API layer. While the JavaScript wars mean that front end frameworks are in flux all the time, Ruby feels like a far more stable choice for architecting an API that people will be able to work on and contribute to easily. I'll be interested to see how Ruby adapts and changes to high-performing (read: much faster) languages, like Rust. Personally, I'm keeping my eye on things like Helix, which makes the future of Ruby seem super bright.
I agree - I think Ruby's future lies more as an API layer, .
Haven't tried Helix yet, but it looks most interesting.
For me, at the end of the day it comes down to a simple fact - I like Ruby.
So if it's my choice, and it seems a good fit, I use Ruby.
Helix looks way further along than when I last heard about it. That is absolutely going to be a big boon for Ruby.
I asked this question because I have a hard time articulating why I stick with Ruby. DHH's keynote which touched on culture said a lot, but I still am not sure. A couple months ago I wrote a classic Ruby bug where I passed the wrong value to a method and it really made me yearn for some stronger typing.
In many ways Ruby fits my personality and I get what DHH often says about the community and culture, but I often feel at odds with it, like intellectually.
Thanks for a really well-articulated view.