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

121–130 of 132 posts

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

#121

Post by melony »

sergiotapia wrote: post #92
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 recently tried Nextjs and Remix to explore other stacks since I've been using Elixir and Phoenix since 2016. You won't find the dev UX you take for granted in Elixir and Phoenix. Endless routing options, background jobs? Just install Squirrel and yadabadabadoo or just use AWS SQS( https://old.reddit.com/r/nextjs/comments/qspw4v/how_to_do_ba... ). What about solid backend processes? Can I call those in some kind of…

The counter argument is that you don't have to babysit any of those services. AWS/some other PaaS will handle everything for pennies. Unless you are working in a low cost of labor country, developer time is going to be more expensive than anything else. It will take very large scale/growth for infrastructure fees to exceed the total compensation of a decent US staff engineer or a site reliability engineering team.

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

#122

Post by multiplegeorges »

treis wrote: post #112
mike1o1 wrote: post #67

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

I've got two problems with Rails: (1) IMHO they've flubbed the progressive typing. I'm spending some time learning Typescript and React. And it's amazing. The type system is flexible, powerful, and works well with an IDE. It's just way faster to write when code gets complexer. The fact that it's null and type safe is the cherry on the top. Amazing that Javascript with all of it's warts can be turned into this. (2) Th…

1 has nothing to do with Rails. Rails is a framework, Ruby is the language.

As for 2, I see this as a common complaint, but Hotwire, Turbo Streams with ViewComponent is a really power combination whose full potential is still being worked out.

As for client-side error checking... why? So I have to maintain validations in two places and ensure they always match?

I don't even understand your 3. Rails has no UI. Do you mean the CSS applied to the scaffolding views?

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

#123

Post by multiplegeorges »

brink wrote: post #10
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?

> What's the general vibe on RoR nowadays? Most people that use it are fine and productive. Because of lazy evaluation, type issues persist though. Plenty of instances of trying to call string methods on integers, and array methods on nil, and Rails devs in denial that that's a big problem as the app continues to grow.

I've just added Sorbet and Tapioca to a Rails project and I was pleasantly surprised to find out that it works very well now!

As I add type annotations to my methods, VS Code and Sorbet are giving me similar feedback to what I get from Typescript projects.

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

#124

Post by multiplegeorges »

bambataa wrote: post #60
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?

What are you using for full stack Typescript? I’m not aware of anything as batteries included as Rails.

There isn't one. RedwoodJS or Blitz come closest, IMO.

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

#125

Post by [deleted] »

multiplegeorges wrote: post #122
treis wrote: post #112

Earlier quoted context omitted.

I've got two problems with Rails: (1) IMHO they've flubbed the progressive typing. I'm spending some time learning Typescript and React. And it's amazing. The type system is flexible, powerful, and works well with an IDE. It's just way faster to write when code gets complexer. The fact that it's null and type safe is the cherry on the top. Amazing that Javascript with all of it's warts can be turned into this. (2) Th…

1 has nothing to do with Rails. Rails is a framework, Ruby is the language. As for 2, I see this as a common complaint, but Hotwire, Turbo Streams with ViewComponent is a really power combination whose full potential is still being worked out. As for client-side error checking... why? So I have to maintain validations in two places and ensure they always match? I don't even understand your 3. Rails has no UI . Do you…

[deleted]

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

#126

Post by bradgessler »

ghiculescu wrote: post #90

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.

I’m stoked about this. It will make it even easier to support deployments to https://fly.io/ and other Docker platforms.

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

#127

Post by tomca32 »

0x457 wrote: post #100
jonahx wrote: post #99

Earlier quoted context omitted.

You can like rails, but calling it boringly simple is highly misleading. I think, generously, something like "complex but fully-featured" might be accurate. As a reference point, the top 2 rails books on amazon are 900 and almost 1100 pages. I say this to warn those who are looking for something minimalist and quick to learn -- Rails does not fit the bill.

nah, at this point RoR is boring (in a good way), and it's a good thing.

Boring in a good way, absolutely. Definitely not simple though

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

#128

Post by gls2ro »

mplewis wrote: post #45
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?

Rails is unfortunately much slower, and it’s quite coupled to the concepts of server-side rendering and OOP MVC. Making Rails work with a modern frontend feels pretty hacky compared to using a full-stack TypeScript framework.

Because maybe other people might read this:

Rails are good enough to keep Shopify standing for another year of holiday sales. It seems to do that since 2006, so this alone demonstrates that Rails can support you a long way in your multi-billion business.

And if you think: "yes, but Shopify has a big talented team," I feel the need to say back, "Well, when you are at Shopify business size, you will have it too. And Shopify used it when they were small too."

I am not saying Rails fits everything, but if your business fits Rails, that is a great framework to build with.

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

#129

Post by fomine3 »

melony wrote: post #121
sergiotapia wrote: post #92

Earlier quoted context omitted.

I recently tried Nextjs and Remix to explore other stacks since I've been using Elixir and Phoenix since 2016. You won't find the dev UX you take for granted in Elixir and Phoenix. Endless routing options, background jobs? Just install Squirrel and yadabadabadoo or just use AWS SQS( https://old.reddit.com/r/nextjs/comments/qspw4v/how_to_do_ba... ). What about solid backend processes? Can I call those in some kind of…

The counter argument is that you don't have to babysit any of those services. AWS/some other PaaS will handle everything for pennies. Unless you are working in a low cost of labor country, developer time is going to be more expensive than anything else. It will take very large scale/growth for infrastructure fees to exceed the total compensation of a decent US staff engineer or a site reliability engineering team.

A problem is that "penny" isn't actually penny for hobby or very small internal in-corp project.

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

#130

Post by firecall »

flakeoil wrote: post #59
angelmm wrote: post #9

Earlier quoted context omitted.

At the backend side, it makes easy to build websites. However, the UI layer is a bit complex to integrate with common framework libraries like Vue and React. Although, I still use it in some projects :)

I'm not sure why you think it's difficult to integrate with Vue and React? Maybe InertiaJS [0] would help. [0] https://inertiajs.com/

Would you use this instead of Hotwire?
Post reply on HN