Live data from Hacker News

Ask HN: Is Ruby on Rails still worth it?

news.ycombinator.com

1–10 of 80 posts

Re: Ask HN: Is Ruby on Rails still worth it?

#2
Yes. It's still a very good framework for simple Web Apps. It's takes care of a lot of boilerplate.

With Rails 5, it's good for a simple API backend as well. And there are a ton of gems that can alleviate a lot of pain.

It's when something non trivial where Rails may not be a good choice.

Re: Ask HN: Is Ruby on Rails still worth it?

#3
In my opinion, yes. I recently built a recent project in Rails 5 and it was rock solid. As your JS needs evolve or you want to start from scratch with a JS framework you can even use Webpacker to introduce Vue or React into your app easily and manage dependencies with Yarn.

Re: Ask HN: Is Ruby on Rails still worth it?

#5

In my opinion, yes. I recently built a recent project in Rails 5 and it was rock solid. As your JS needs evolve or you want to start from scratch with a JS framework you can even use Webpacker to introduce Vue or React into your app easily and manage dependencies with Yarn.

This. Webpacker enormously improved the JS experience with Rails.

Re: Ask HN: Is Ruby on Rails still worth it?

#7
Wouldn't Python/Django make more sense in 2018 considering that Python could be used for data science and machine learning? I realize this is a Python vs Ruby question, but if you didn't know either Python or Ruby and were trying to pick between Django and Rails for a project, wouldn't you pick Django in 2018 due to future data science and machine learning opportunities?

Re: Ask HN: Is Ruby on Rails still worth it?

#9
Absolutely. If you're building a POC or MVP it's a quick and easy way to get something off the ground. The framework will take you pretty far before you have scaling issues (long enough to know if what you're making is worth it). The community is very knowledgeable and friendly, and gems for almost everything already exist.

If I needed to spin up a new project and get to work right away on something I'd go with rails no question. I've yet to find another language/framework combo that works as well as a Ruby & Rails stack (Laravel and Django are good alternatives too, I'm just more experienced with Ruby). Don't think too far ahead. Premature optimization or thinking about future scaling issues if starting a new project is time that could be spent better. Rails isn't going anywhere anytime soon.

Post reply on HN