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

61–70 of 132 posts

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

#61

Post by jmondi »

Mikeb85 wrote: post #53
stevebmark wrote: post #46

> 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.

> 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. Have you not paid attention to the direction Rails is going? Hotwire (Rails' default front end) is all amount rendering HTML directly (not via JS) and using the absolute bare minimum amount of vanilla Javascript (with Stimulus). It's n…

If Hey has shown me anything, it is that Hotwire IMO is a complete gimmick. The frontend of Hey had so many issues for me. I used used hey from release until about a month or two ago, and it was the terrible UXUI experience that pushed me to cancel. Weird loading issues, things would update after performing actions, not loading in place correctly etc.

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

#62

Post by Alifatisk »

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 have to agree on this one, it feels like some people are in denial of type issues within the Ruby / Rails community.

I've been experimenting with Rbs, Sorbet & Contracts though, they have their potential.

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

#63

Post by fknorangesite »

flippinburgers wrote: post #38
brink wrote: post #10

Earlier quoted context omitted.

> 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.

The main problem is active record insanity and poorly designed table relationships/indices that lead to maintenance nightmares.

> poorly designed table relationships/indices that lead to maintenance nightmares.

Like what?

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

#65

Post by ithrow »

redox99 wrote: post #56
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 technologies exactly do you use in your full stack typescript?

nodejs, postgres and react?

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

#66

Post by stevebmark »

Mikeb85 wrote: post #53
stevebmark wrote: post #46

> 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.

> 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. Have you not paid attention to the direction Rails is going? Hotwire (Rails' default front end) is all amount rendering HTML directly (not via JS) and using the absolute bare minimum amount of vanilla Javascript (with Stimulus). It's n…

My post was mostly in jest. I’m well aware the “method_missing” crew has no desire to statically analyze their programs.

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

#67

Post by mike1o1 »

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/

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

#68

Post by stevebmark »

jmondi wrote: post #61
Mikeb85 wrote: post #53

Earlier quoted context omitted.

> 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. Have you not paid attention to the direction Rails is going? Hotwire (Rails' default front end) is all amount rendering HTML directly (not via JS) and using the absolute bare minimum amount of vanilla Javascript (with Stimulus). It's n…

If Hey has shown me anything, it is that Hotwire IMO is a complete gimmick. The frontend of Hey had so many issues for me. I used used hey from release until about a month or two ago, and it was the terrible UXUI experience that pushed me to cancel. Weird loading issues, things would update after performing actions, not loading in place correctly etc.

If you think Hey’s UI is bad, you should try Basecamp

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

#69

Post by drchiu »

ezekg wrote: post #6

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

Yup, I was hoping this would make it to 7-1 but I suppose there were too many cases to consider.

I wonder if certain features could be marked as "experimental" by Rails core like they do in Ruby, and include them without the promise that the API would be stable (or even be present at all in the future).

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

#70

Post by andrei_says_ »

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’ve never seen a more productive stack. Enables me to build complete apps as a single dev - which would take 2x-5x of the time and effort if using separate front end apps. Ruby makes me happy when I use it. Hotwire and Stimulus let me create front end interactions without a separate SPA. The ecosystem is mature and well maintained. Absolutely love it.
Post reply on HN