Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

web.archive.org

Post reply on HN
Print view View original

11–20 of 132 posts

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#11

Post by aliqot »

cguess wrote: post #8
aliqot wrote: post #5

Quoted post unavailable.

Shopify and Github being run on Rails sorta put it to bed a long time ago.

It really didn't otherwise there would be a lot more than just those two, everyone would follow their beat. We all ran rails 10 years ago and realized that unless you're a large corp with money to burn on 'ecosystem' then Rails doesn't make a lot of sense.

I want to like rails and to see it do well, but it's not keeping pace with the rest of its peers. As competitive as web dev is these days, it's not sufficient to just be rails, you need a ruby alternative to rails as well. Look at javascript. Nobody uses javascript straight up, there's a multitude of rails-like frameworks for javascript. A new one is made each day, and they have staying power.

Ruby has Rails, and some might argue that metaphorically speaking Rails has Ruby, by its polite little balls. Unfortunately Rails's star power is outliving Ruby's and given that new Ruby devs aren't being born every day, it's not hard to see that that's bad for Rails.

I'd love to see rails move to JS or Elixir or something that'll get people interested in it again, and KEEP them this time by being written in something fast.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#12

Post by kshahkshah »

brntsllvn wrote: post #2

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?

I love TypeScript, but Rails has a wonderful ecosystem of libraries that just feels unbeatable for the backend. For some reason (hot take incoming) the JS community seems to hate working with each other and improving existing libraries. The Ruby community seems to rally around improving our libraries (gems) rather than reinventing them every year.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#14

Post by Alifatisk »

angelmm wrote: post #7

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 comm…

Rails do support frontend frameworks like Vue if you wish to create more interactive & advanced UI's.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#19

Post by marlomajor »

texxtxxet wrote: post #17

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?

Better. Much, much better than webpack/vite imo.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#20

Post by DiNovi »

aliqot wrote: post #11
cguess wrote: post #8

Earlier quoted context omitted.

Shopify and Github being run on Rails sorta put it to bed a long time ago.

It really didn't otherwise there would be a lot more than just those two, everyone would follow their beat. We all ran rails 10 years ago and realized that unless you're a large corp with money to burn on 'ecosystem' then Rails doesn't make a lot of sense. I want to like rails and to see it do well, but it's not keeping pace with the rest of its peers. As competitive as web dev is these days, it's not sufficient to j…

so much of the web is php and rails it just feels alien to see this kind of thought process
Post reply on HN