Why I believe Rails is still relevant in 2019 • Hacker News Board

Re: Why I believe Rails is still relevant in 2019

#261

Post by pankajdoharey » Thu, Mar 21, 2019, 7:26 AM UTC

Retra wrote: post #224

pankajdoharey wrote: post #85

Mostly an opinion piece, A few points to Observe : * According to the author NodeJS fails architecturally when small amounts of complexity is added to it. => Same applies to Rails aswell, anything beside a crud app and you start wondering which code goes where. * Rails is Opinionated... => Great if it were 2006, In 2019 rest apis are a norm, and more Nodejs apps get enabled everyday have the same feature. Infact serv…

Are you really choosing web frameworks based on how 'innovative' they are?

Innovation implies improvement! My primary metric is ease of use and long term scalability, but so is constant improvement and upgradation in features. A rich text editor isnt improvement, its bloatware.

Re: Why I believe Rails is still relevant in 2019

#262

Post by nathan_long » Thu, Mar 21, 2019, 5:39 PM UTC

JangoSteve wrote: post #216

nathan_long wrote: post #199

Earlier quoted context omitted.

> Perhaps you don't want everything eager loaded, but you want an exception to be raised if you try to access an associated record that hasn't been preloaded. Yes, exactly. > When I need to load/use them along with many parent records, it seems pretty obvious that I'll want to include those associations (eagerly loaded) in my AR query to avoid N+1 queries as you mentioned. Then again, maybe I've just spent too long t…

Looks like the bullet gem does what you want. https://semaphoreci.com/blog/2017/08/09/faster-rails-elimina... https://github.com/flyerhzm/bullet EDIT: It looks like this was already mentioned in another thread. I guess I don't understand the issue if that doesn't solve your problem.

The bullet gem has helped me solve this problem in specific applications before, yes.

My higher-level problem is that having lazy-loading on by default allows N+1 queries to creep in to a code base and you need a third-party gem to find them. I've had to spend significant time finding and fixing this after joining teams with large legacy apps.

"Disable lazy loading globally" should be an ActiveRecord setting and it should be on by default IMO; people who need lazy loading should have to turn it on per query, something like `query.allow_lazy_loading(post: :author)`. I suspect that a very small fraction of queries would use this, since many apps don't do server side rendering, many who do SSR don't use Russian doll caching, and even those who do both still execute many queries that should prefetch all the associations they use.

Re: Why I believe Rails is still relevant in 2019

#263

Post by goobynight » Thu, Mar 21, 2019, 8:35 PM UTC

lmm wrote: post #107

fouc wrote: post #9

All the standard web technologies are still relevant. MySQL & PostgreSQL are still relevant. Redis is still relevant. Ruby on Rails is still relevant. Javascript is still relevant.

Disagree with all of those except Javascript (and that only as an execution layer). All of the things that those technologies promised, we now have better ways of achieving.

What are the better ways?

Re: Why I believe Rails is still relevant in 2019

#264

Post by andrei_says_ » Fri, Mar 22, 2019, 1:10 AM UTC

geebee wrote: post #225

This particular blog post did a fine job articulating the benefits of Rails, and these remain good reasons to use rails in 2019. I think there's another side of this discussion. There are reasons why rails itself is worth using, and then there are reasons why MVC frameworks + a sprinkling of javascript are still worth using. Personally, I feel that the latest trend toward heavy javascript front ends that are more or…

Just so you know, agree on all counts :)