from Hacker News

An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

by siaw23 on 12/20/22, 3:02 PM with 124 comments

• by ghiculescu on 12/20/22, 5:37 PM

  I have a feeling the big picture theme for 7.1 will be Docker. See https://github.com/rails/rails/pull/46762 for production, and https://github.com/rails/docked for development.

• by mike1o1 on 12/20/22, 5:00 PM

  I love Rails and how simple and boring[0] it is, and appreciate how it keeps evolving and growing. I've dabbled with some Javascript frameworks and Elixir/Phoenix, but always come back to Rails and forget just how fast and productive I can be. A lot of people complain about it, but I feel like Active Record just can't be beat, and helps me feel so productive. Add Stimulus and Turbo and the level of UI fidelity possible is impressive.

  [0] https://boringrails.com/

• by ezekg on 12/20/22, 3:29 PM

  I was pretty sad to see the pattern matching PR reverted for 7.1 [0], but I guess the Rails team wants to make sure they nail the execution (?) even if that means being late to the pattern matching party, which is arguably one of the best additions to Ruby since the 1.9.3 hash syntax.

  For now, I'm good with the little gem that kddnewton put together (https://github.com/kddnewton/rails-pattern_matching).

  [0]: https://github.com/rails/rails/pull/45553

• by brntsllvn on 12/20/22, 3:26 PM

  I was a devoted rails fan 10 years ago, but haven't looked back since full stack typescript.

  What's the general vibe on RoR nowadays?

• by angelmm on 12/20/22, 3:31 PM

  Great to see so many new features in Rails. Tbh, one of the reasons I use it for certain backend projects is how simple to do complex things.

  Managing files and image variants is a pain when developing a site. Rails make it easy and even adds more features around.

  However, I still think the UI layer is too coupled to the backend. Webpacker was a try, but I understand why it's deprecated. I would go on supporting common frameworks, even if it's just a template to organize the code.

• by systems_glitch on 12/20/22, 3:56 PM

  Finally upgraded some internal applications to Rails 7 this month, and I was very happy with the asset pipeline changes. Rails' asset pipeline management hasn't really meshed with our development strategies for CSS and JS for a long time, and it felt like we were always fighting with trying to make our process fit Rails' expectations.

  We're on Propshaft now and I expect far fewer asset issues in the future :P

• by juanse on 12/20/22, 3:29 PM

  I am really excited about the possibility that Rails finally get something in the way of ActiveDeployment. This tweet https://twitter.com/dhh/status/1604856555848884225 and the commited changes make me wish and wonder.

• by texxtxxet on 12/20/22, 3:41 PM

  1. Rails retired Webpacker [that] compiled and bundled JS. Import maps, Turbo and Stimulus [are now the] default options, replacing Webpacker, Turbolinks and UJS.

  How do these new tools compare with the old? Versus Webpack, Vite etc?

• by stevebmark on 12/20/22, 4:18 PM

  > Later in the year, Rails retired Webpacker

  Is Rails anti Typescript? It’s weird to see most other JS environments move to Typescript by default, while Rails now now ignores the ability to use it without jumping through hoops.