There is a lot of discussion about the Ruby language demise. Well, this balderdash is circulating for a while now, and there are posts from 3+ years ago saying that Ruby is dead, but in fact, here we are.
A Google Trends search shows that the Ruby interest over time isn’t decaying, but following the same pattern similar technologies are tracing. Also, always keep in mind that programming languages are tools to solve specific problems, and that is why there is no such thing as the best programming language.
Ruby has gone through a lot of significant changes during the past year, and it is certainly not dying, but growing and evolving. The year of 2019 has a lot to the Ruby community. Check some of the key points below:
Ruby 2.6 and its new JIT compiler
A new version of Ruby has been released in December 2018. This release includes a lot of performance improvements and new features, including an initial implementation of a JIT (Just-In-Time) compiler.
To say truly, this new JIT compiler has not achieved its best performance yet, as covered here, but has a lot of future on it. The Ruby community considers this release as an opening to the new era of Ruby.
While I failed to make Ruby’s JIT production-ready in 2.6, I don’t regret what we’ve done this year. I needed to develop or lead all of the above things for Ruby 2.6, but I believe I can invest my time mainly on performance improvement in Ruby 2.7. — @k0kubun
Besides this new JIT compiler, this new release of Ruby has improved performance up to 1.7x, apart from the 5–10% performance improvements from Ruby 2.5.0.
Ruby on Rails new release is getting close
Ruby on Rails 6 is close. This release includes a lot of cool features that will get web development much easier, as Rails has been doing for years.
2018 has brought a major release, Rails 5.2.x, that included:
Active Storage, a modern approach of uploading files straight to the cloud.
Redis cache-store
HTTP/2 Early Hints
Credentials, a new and secure way to store secrets
And now, with Rails 6, there are a lot of exciting features, such as:
Action Mailbox, a new way to serve to route incoming emails to controller-like mailboxes for processing in Rails
Action Text, bringing the Trix editor to the framework
Parallel testing, allows you to parallelize your test using forks or threads
Webpack as the default JavaScript bundler
Ruby isn’t dying, it’s maturing
Yes, Ruby was bad and Rails was slow. But that is not true to say in 2018, and won’t be in 2019. Ruby isn’t slow and Rails does scale. If it doesn’t for you, maybe you’ve chosen the wrong tools for the problem you’ve got.
In 2019, let’s enjoy programming Ruby 2.6 and Rails 6! Happy New Year!
Top comments (20)
Jorge, Ruby is a language, not an IDE. There’s no such thing as official IDE for Ruby. You just need the Ruby runtime and an editor (I use Vim, for instance).
Also, why C# is the “fastest to program”? I’ve never seen statically typed languages as the “fastest to program”.
Again, it always depends on the problem you’re trying to solve. There’s no such thing as the best programming language. It depends on the problem you’ve got.
Data say you’re wrong. Just search for jobs on Stack Overflow Jobs and you’ll see the amount of back-end openings for Ruby.
Also, dev.to and GitHub are built with Rails.
@jorge Castro
Every job listing site is misleading due to the compartmentalization inherent in using a job site.
Why is working for a small company/startup not valid? The same problems apply and the paycheck clears the bank. Not everyone likes waiting 3 months for SSH access to a non-prod environment (big orgs). As for locationali availability; It's 2019; location is almost the smallest bearer to overcome in terms of employment.
Languages, IDEs, OSes, Job Sites, etc are all tools. Our goal as developers should be singularly focuses on leveraging the correct tools that provide business value.
I think Square's web app is also Ruby.
And gitlab
I came to Ruby and Rails (for a job) in 2018 and I couldn’t disagree more. The comments above about productivity are spot on.
To use your analogy, even if some store isn’t the best place to get any one given thing, it can still be the best place to go when you need 15 different things (particularly if you don’t quite know what they are yet)
I'd say it's still the best in regards to web-dev productivity.
What can I say @JorgeCastro, your remarks on three languages seems far and between the hypothesis that exists only on your head. Webforms really!! What are we developing a web page?
PHP king of the hill, oh my Lord.
Sorry can't help but highlight your personal opinion might need slight adjustment as to what is fastest, king and power machine.
Ruby and Rails are alive and well. They might not be the best technologies for everything and everyone but Rails 6 and Ruby 3x3 are exciting news!
ps. your link "Ruby on Rails 6 is close" doesn't work...
Well, nothing is the best technology for everything and yes - Ruby and Rails are no different here. There are areas where Rails will still be the best fit with pretty much no competition.
Definitely not. It's not as "hot" as it once was, but people are quietly getting lots of shit done with it everyday.
Cool, I'll make sure I check that out the next time I want something to look like a 1990s Oracle application.
That seems like a foolish opinion on any tool. I also disagree with your first point, pretty strongly. Ruby is still quite popular. It's also one of the higher paying technologies.
Do you have anything other than anecdotal experience to back that opinion up?
The only real argument I've heard against Ruby as a career move is that it requires you to compete with very experienced, high-quality developers for jobs.
What is “ready to use”? You can literally run two commands to get ruby installed and your repo either pulled or deployed with something like Capistrano. In fact, if you’re not using VPS or lambdas for your applications at this point, I would solidly and unequivocally say you have no idea what you’re doing, and your other [inflammatory] posts on this site suggest as much as well.
I’m not saying there’s no room for preference, but your point about PHP being ready to use is literally 100% invalid.
Whaaat are you talking about? You can't just generalize a statement like that without providing one iota of evidence--even if it's opinion. I've been around quite a few blocks in terms of types of web development technologies, and just nothing allows me to be more productive than RoR. Sure, I may lean on Node.js when it's inherently better at a problem, but I just don't think a better holistic full-stack web development framework exists.