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

Re: Why I believe Rails is still relevant in 2019

#171

Post by emptyroads » Tue, Mar 19, 2019, 2:44 PM UTC

nathan_long wrote: post #157

I spent a couple of years dreaming of getting paid to work in Ruby and Rails and about 7 years doing so. There are many things I loved about Ruby, and Rails brought a ton of good ideas to web development, as this post describes (though I don't agree with all the highlights). I've since moved to using Elixir and Phoenix, and then even more recently, done some consulting on a Rails project. So the contrasts are on my m…

I agree with a lot of what you've described, but 7 years of working in Rails and you never figured out how to turn off lazy loading in ActiveRecord?

Re: Why I believe Rails is still relevant in 2019

#172

Post by KurtMueller » Tue, Mar 19, 2019, 2:47 PM UTC

nathan_long wrote: post #157

I spent a couple of years dreaming of getting paid to work in Ruby and Rails and about 7 years doing so. There are many things I loved about Ruby, and Rails brought a ton of good ideas to web development, as this post describes (though I don't agree with all the highlights). I've since moved to using Elixir and Phoenix, and then even more recently, done some consulting on a Rails project. So the contrasts are on my m…

> chasing down N+1 queries to improve performance is something I spent far too many hours doing

Just an FYI for any Rails dev reading this, the Bullet gem is excellent for pointing out n+1 queries.

Re: Why I believe Rails is still relevant in 2019

#173

Post by crb002 » Tue, Mar 19, 2019, 2:48 PM UTC

Rails will have a resurgence with a Data Driven Design generator like JHipster. So much time saved when you get front end client side validations generated automatically; and layout is 90% automated with UI constraints.

Re: Why I believe Rails is still relevant in 2019

#174

Post by desireco42 » Tue, Mar 19, 2019, 2:49 PM UTC

nathan_long wrote: post #157

I spent a couple of years dreaming of getting paid to work in Ruby and Rails and about 7 years doing so. There are many things I loved about Ruby, and Rails brought a ton of good ideas to web development, as this post describes (though I don't agree with all the highlights). I've since moved to using Elixir and Phoenix, and then even more recently, done some consulting on a Rails project. So the contrasts are on my m…

Hey, I am so glad to hear this. My sentiments are somewhat similar. My Elixir project didn't get traction so I am back to Rails and some other tech, but definitely Elixir is the future. Now as far as Rails go, this can be my super power.

I see a lot of Nodejs project struggle and reinvent things that people in Rails community take for granted. Like Nuxt.js for example.

Re: Why I believe Rails is still relevant in 2019

#175

Post by lmm » Tue, Mar 19, 2019, 2:50 PM UTC

toasterlovin wrote: post #163

lmm wrote: post #105

Earlier quoted context omitted.

A summary of my experience would be: libraries are good, frameworks are bad. (Indeed possibly the best "framework" I ever used was TurboGears which is very deliberately just a collection of dedicated libraries, all of which you can replace piecemeal as and when you need to). Rails raised the bar for how little custom configuration should be necessary to do a simple, straightforward thing. But it turns out being a fra…

You know that Rails is a collection of libraries that can pretty much all be replaced with the alternative of your choice, right?

Up to a point. In my experience there is limited support for e.g. using "mismatched" versions of different parts of it.

Re: Why I believe Rails is still relevant in 2019

#176

Post by KurtMueller » Tue, Mar 19, 2019, 2:51 PM UTC

StevePerkins wrote: post #167

What is the Ruby community like in 2019? I've spent the past 20 years primarily working on JVM-based languages. Being told for about 19 of those years that my boring verbose tech stack stack is obsolete, and going away from the business world any day now. Most recently, that voice comes mainly from the Node.js community. But 10 years ago, it was a mix of Ruby and Python upstarts. I kinda saw those languages and commu…

These are certainly broad categories you're putting people into. I'm a ruby developer who wears t-shirts and jeans on the regular, have no tattoos, and shave with a Gillette Mach 3 razor (lol).

I'm definitely older and more mature now but I'd don't necessarily think that makes it closer to the Python community culturally nor that the two dev communities were ever that far apart to begin with.

Re: Why I believe Rails is still relevant in 2019

#177

Post by nathan_long » Tue, Mar 19, 2019, 2:51 PM UTC

KurtMueller wrote: post #172

nathan_long wrote: post #157

I spent a couple of years dreaming of getting paid to work in Ruby and Rails and about 7 years doing so. There are many things I loved about Ruby, and Rails brought a ton of good ideas to web development, as this post describes (though I don't agree with all the highlights). I've since moved to using Elixir and Phoenix, and then even more recently, done some consulting on a Rails project. So the contrasts are on my m…

> chasing down N+1 queries to improve performance is something I spent far too many hours doing Just an FYI for any Rails dev reading this, the Bullet gem is excellent for pointing out n+1 queries.

Yep, I used it extensively on one project, configuring it to raise exceptions if it detected an N+1 query and gradually enabling it test by test as I fixed them. It's very helpful.

Re: Why I believe Rails is still relevant in 2019

#178

Post by nathan_long » Tue, Mar 19, 2019, 2:52 PM UTC

emptyroads wrote: post #171

nathan_long wrote: post #157

I spent a couple of years dreaming of getting paid to work in Ruby and Rails and about 7 years doing so. There are many things I loved about Ruby, and Rails brought a ton of good ideas to web development, as this post describes (though I don't agree with all the highlights). I've since moved to using Elixir and Phoenix, and then even more recently, done some consulting on a Rails project. So the contrasts are on my m…

I agree with a lot of what you've described, but 7 years of working in Rails and you never figured out how to turn off lazy loading in ActiveRecord?

I know how to preload associations, but I don't know how to globally disable lazy loading of associations. Do you know a way?

Re: Why I believe Rails is still relevant in 2019

#179

Post by KurtMueller » Tue, Mar 19, 2019, 2:53 PM UTC

jypepin wrote: post #47

yedpodtrzitko wrote: post #8

Earlier quoted context omitted.

I replaced `rails` with `Django` in your statement (and maybe could do the same with Node.js), and it reads the same. Guess it's just about being familiar with a mature ecosystem you already know, and then you can achieve results.

Agreed. Although I do Rails and have no experience with Django I know Django is the same. To my knowledge tho, I do believe those are the only 2 framework that offer so many plug-and-play, trustable component for everything, allowing you to be up and running so fast. I've built similarly large systems both with rails, flask and nodejs. Nodejs environment was definitely the worst, on every front, and I coming back to…

> To my knowledge tho, I do believe those are the only 2 framework that offer so many plug-and-play, trustable component for everything, allowing you to be up and running so fast.

asp.net? I'm asking because I don't know.

Re: Why I believe Rails is still relevant in 2019

#180

Post by gumcreme » Tue, Mar 19, 2019, 2:54 PM UTC

jashmatthews wrote: post #142

gumcreme wrote: post #103

Earlier quoted context omitted.

Well framed and this is what we all learned and moved to: There are new paradigms out that just make so much more sense and which are followed by the majority. When I read the original submission, I mean just the title, I was facepalming in my mind. Rails had its time and there were reasons why people liked it. But when I see that people post that Rails is still great in 2019, I'd like to stress following issue becau…

> proper http/2 support in Rails-land Between early hints support in Rails 5.2, nginx proxying to HTTP2, and an http2 enabled CDN what's actually missing?

ngninx supporting http/2 != Rails supporting http/2

Depending on the use case you leave out nginx sometimes, eg. when doing microservices. Not that nginx is bad but with other stacks you very often don't need nginx and/or connect directly to the CDN reducing complexity in a stack.